Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-1623 High Availability Framework for HDFS NN
  3. HDFS-2894

HA: automatically determine the nameservice Id if only one nameservice is configured

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: HA branch (HDFS-1623)
    • Fix Version/s: None
    • Component/s: ha
    • Labels:
      None

      Description

      The SecondaryNameNode should log a message and refuse to start if HA is enabled since the StandbyNode checkpoints by default and IIRC we have not yet enabled the ability to have multiple checkpointers in the NN.

      On the HA branch the 2NN does not currently start from start-dfs.sh because getconf -secondarynamenodes claims the http-address is not configured even though it is, though this seems like a bug, in branch 23 getconf will correctly return localhost:50090.

       <property>
         <name>dfs.namenode.secondary.http-address</name>
         <value>localhost:50090</value>
       </property>
      
      </configuration>
      hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs getconf -secondarynamenodes
      Incorrect configuration: secondary namenode address dfs.namenode.secondary.http-address is not configured.
      

        Attachments

        1. hdfs-2894.txt
          11 kB
          Eli Collins
        2. hdfs-2894.txt
          13 kB
          Eli Collins

          Issue Links

            Activity

              People

              • Assignee:
                eli Eli Collins
                Reporter:
                eli2 Eli Collins
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: