Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-12402

Make CatalogdMetaProvider's cache concurrency level configurable

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Patch
    • ghx-label-12

    Description

      when the cluster contains many db and tables such as if there are more than 100000 tables, and if we restart the impalad , the local cache_ CatalogMetaProvider's need to doing some loading process.
      As we know that the goole's guava cache 's concurrencyLevel os set to 4 by default.
      but if there is many tables the loading process will need more time and increase the probability of lock contention, see here.
      So we propose to add some configurations here, the first is the concurrency of cache.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            maxwellguo Maxwell Guo
            maxwellguo Maxwell Guo
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment