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

Bound the size of Impalad catalog cache

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

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Duplicate
    • Impala 2.5.0
    • None
    • Catalog

    Description

      Currently the catalog cache of every Impalad holds a replica of the entire catalog. In certain scenarios (e.g. large metadata), the local catalog cache is using memory that could be used more effectively elsewhere. We should consider changing the impalad catalog cache into a proper cache with a configurable size limit and an invalidation mechanism.

      Attachments

        Issue Links

        Activity

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

          People

            Unassigned Unassigned
            dtsirogiannis Dimitris Tsirogiannis
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment