Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-14412

HostsFileReader#getHostDetails is very expensive on large clusters

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.8.0
    • 2.9.0, 3.0.0-alpha4, 2.8.2
    • util
    • None
    • Reviewed

    Description

      After upgrading one of our large clusters to 2.8 we noticed many IPC server threads of the resourcemanager spending time in NodesListManager#isValidNode which in turn was calling HostsFileReader#getHostDetails. The latter is creating complete copies of the include and exclude sets for every node heartbeat, and these sets are not small due to the size of the cluster. These copies are causing multiple resizes of the underlying HashSets being filled and creating lots of garbage.

      Attachments

        1. HADOOP-14412.001.patch
          18 kB
          Jason Darrell Lowe
        2. HADOOP-14412.002.patch
          18 kB
          Jason Darrell Lowe
        3. HADOOP-14412-branch-2.001.patch
          18 kB
          Jason Darrell Lowe
        4. HADOOP-14412-branch-2.002.patch
          18 kB
          Jason Darrell Lowe
        5. HADOOP-14412-branch-2.002.patch
          18 kB
          Jason Darrell Lowe
        6. HADOOP-14412-branch-2.8.002.patch
          16 kB
          Jason Darrell Lowe

        Issue Links

        Activity

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

          People

            jlowe Jason Darrell Lowe
            jlowe Jason Darrell Lowe
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment