hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-2894) HA: automatically determine the nameservice Id if only one nameservice is configured
Date Mon, 06 Feb 2012 08:29:59 GMT

     [ https://issues.apache.org/jira/browse/HDFS-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eli Collins resolved HDFS-2894.
-------------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed

Thanks for the review Todd. I've committed this.
                
> HA: automatically determine the nameservice Id if only one nameservice is configured
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-2894
>                 URL: https://issues.apache.org/jira/browse/HDFS-2894
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: hdfs-2894.txt, hdfs-2894.txt
>
>
> 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.
> {noformat}
>  <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.
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message