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

If dfs.http.address is default, SecondaryNameNode can't find NameNode

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.21.0
    • fs
    • None

    Description

      As detailed in this blog post:
      http://www.cloudera.com/blog/2009/02/10/multi-host-secondarynamenode-configuration/
      if dfs.http.address is not configured, and the 2NN is a different machine from the NN, the 2NN fails to connect.

      In SecondaryNameNode.getInfoServer, the 2NN should notice a "0.0.0.0" dfs.http.address and, in that case, pull the hostname out of fs.default.name. This would fix the default configuration to work properly for most users.

      Attachments

        1. hadoop-5891.txt
          0.9 kB
          Todd Lipcon

        Activity

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

          People

            tlipcon Todd Lipcon
            tlipcon Todd Lipcon
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment