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

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

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.21.0
    • Component/s: fs
    • Labels:
      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

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: