Uploaded image for project: 'Apache Drill'
  1. Apache Drill
  2. DRILL-1519

Concurrent access to WorkEventBus#getOrCreateFragmentManager leaks memory.

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • None
    • 0.7.0
    • None
    • None

    Description

      WorkEventBus uses a ConcurrentHashMap to ensure there is one and only one FragmentManager corresponding to each unique FragmentHandle. The method creates a FragmentManager that reserves some initial memory if a thread observes that it is not in the map. However, in case of concurrent access, we still need to clean up after if multiple threads observe that FragmentManager does not exist and create multiple FragmentManagers.

      Attachments

        Issue Links

        Activity

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

          People

            DrillCommitter DrillCommitter
            hgunes Hanifi Gunes
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment