Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-5456

NameNode startup progress creates new steps if caller attempts to create a counter for a step that doesn't already exist.

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 2.2.0, 3.0.0-alpha1
    • 2.3.0
    • namenode
    • None
    • Reviewed

    Description

      NameNode startup progress is supposed to be immutable after startup has completed. All methods are coded to ignore update attempts after startup has completed. However, StartupProgress#getCounter does not implement this correctly. If a caller attempts to get a counter for a new step that hasn't been seen before, then the method accidentally creates the step. This allocates additional space in the internal tracking data structures, so ultimately this is a memory leak.

      Attachments

        1. HDFS-5456.1.patch
          2 kB
          Chris Nauroth

        Issue Links

        Activity

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

          People

            cnauroth Chris Nauroth
            cnauroth Chris Nauroth
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment