[
https://issues.apache.org/jira/browse/HDFS-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177538#comment-13177538
]
Eli Collins commented on HDFS-2732:
-----------------------------------
Good point, I missed that. It doesn't work for me since I'm running both the NN
and SBN on the same host, so the 2nd fails to start because the pid file
already exists (other nn already claimed the file). The log dirs would collide
as well. In any case, I don't think we need to support the NN and SBN on the
same host in the start scripts, developers can workaround this by changing the
HADOOP_CONF_DIR and running start-dfs.sh again or start just the NN manually as
I've been doing with a separate conf dir.
> Add support for the standby in the bin scripts
> ----------------------------------------------
>
> Key: HDFS-2732
> URL: https://issues.apache.org/jira/browse/HDFS-2732
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Eli Collins
> Assignee: Eli Collins
>
> We need to update the bin scripts to support SBNs. Two ideas:
> Modify start-dfs.sh to start another copy of the NN if HA is configured. We
> could introduce a file similar to masters (2NN hosts) called standbys which
> lists the SBN hosts, and start-dfs.sh would automatically make the NN it
> starts active (and leave the NNs listed in standby as is).
> Or simpler, we could just provide a start-namenode.sh script that a user can
> run to start the SBN on another host themselves. The user would manually tell
> the other NN to be active via HAAdmin (or start-dfs.sh could do that
> automatically, ie assume the NN it starts should be the primary).
--
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
