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

NameNode in secured HA cluster fails to start if dfs.namenode.secondary.http-address cannot be interpreted as a network address.

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.6.0
    • journal-node, namenode
    • None
    • Reviewed

    Description

      In a secured cluster, the JournalNode validates that the caller is one of a valid set of principals. One of the principals considered is that of the SecondaryNameNode. This involves checking dfs.namenode.secondary.http-address and trying to interpret it as a network address. If a user has specified a value for this property that cannot be interpeted as a network address, such as "null", then this causes the JournalNode operation to fail, and ultimately the NameNode cannot start. The JournalNode should not have a hard dependency on dfs.namenode.secondary.http-address like this. It is not typical to run a SecondaryNameNode in combination with JournalNodes. There is even a check in SecondaryNameNode that aborts if HA is enabled.

      Attachments

        1. HDFS-7359.1.patch
          11 kB
          Chris Nauroth
        2. HDFS-7359.2.patch
          12 kB
          Chris Nauroth
        3. HDFS-7359.3.patch
          13 kB
          Chris Nauroth

        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:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment