hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-2995) start-dfs.sh should only start the 2NN for namenodes with dfs.namenode.secondary.http-address configured
Date Mon, 09 Apr 2012 21:15:16 GMT

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

Todd Lipcon resolved HDFS-2995.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
     Hadoop Flags: Reviewed

Looks like this got committed to trunk and branch-2 last week.
                
> 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
>             Fix For: 2.0.0
>
>         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

        

Mime
View raw message