[
https://issues.apache.org/jira/browse/HDFS-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244211#comment-13244211
]
Hudson commented on HDFS-2995:
------------------------------
Integrated in Hadoop-Mapreduce-trunk #1038 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1038/])
HDFS-2995. start-dfs.sh should only start the 2NN for namenodes with
dfs.namenode.secondary.http-address configured. Contributed by Eli Collins
(Revision 1308174)
Result = FAILURE
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1308174
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/bin/start-dfs.sh
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/bin/stop-dfs.sh
> start-dfs.sh should only start the 2NN for namenodes with
> dfs.namenode.secondary.http-address configured
> --------------------------------------------------------------------------------------------------------
>
> Key: HDFS-2995
> URL: https://issues.apache.org/jira/browse/HDFS-2995
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: scripts
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Todd Lipcon
> Assignee: Eli Collins
> Attachments: hdfs-2995.txt
>
>
> When I run "start-dfs.sh" it tries to start a 2NN on every node in the
> cluster. This despite:
> [todd@c1120 hadoop-active]$ ./bin/hdfs getconf -secondaryNameNodes
> Incorrect configuration: secondary namenode address
> dfs.namenode.secondary.http-address is not configured.
> Thankfully they do not start :)
--
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
