[
https://issues.apache.org/jira/browse/HDFS-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins resolved HDFS-2893.
-------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Thanks Todd and ATM. I committed this and merged. Didn't run test-patch since
it just updates the start/stop scripts. I tested the generated tarball from
branch-23 by hand.
> The start/stop scripts don't start/stop the 2NN when using the default
> configuration
> ------------------------------------------------------------------------------------
>
> Key: HDFS-2893
> URL: https://issues.apache.org/jira/browse/HDFS-2893
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.23.1
> Reporter: Eli Collins
> Assignee: Eli Collins
> Priority: Minor
> Attachments: hdfs-2893.txt
>
>
> HDFS-1703 changed the behavior of the start/stop scripts so that the masters
> file is no longer used to indicate which hosts to start the 2NN on. The 2NN
> is now started, when using start-dfs.sh, on hosts only when
> dfs.namenode.secondary.http-address is configured with a non-wildcard IP.
> This means you can not start a NN using an http-address specified using a
> wildcard IP. We should allow a 2NN to be started with the default config, ie
> start-dfs.sh should start a NN, 2NN and DN. The packaging already works this
> way (it doesn't use start-dfs.sh, it uses hadoop-daemon.sh directly w/o first
> checking getconf) so let's bring start-dfs.sh in line with this behavior.
--
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
