You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/03/02 17:49:05 UTC

[jira] [Updated] (HADOOP-8767) secondary namenode on slave machines

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

Allen Wittenauer updated HADOOP-8767:
-------------------------------------
    Fix Version/s:     (was: 3.0.0)

> secondary namenode on slave machines
> ------------------------------------
>
>                 Key: HADOOP-8767
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8767
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: bin
>    Affects Versions: 1.0.3
>            Reporter: giovanni delussu
>            Assignee: giovanni delussu
>            Priority: Minor
>             Fix For: 1.2.0
>
>         Attachments: patch_hadoop-config.sh_hadoop-1.0.3_fromtar.patch, patch_hadoop-config.sh_slaves.sh_branch1.patch, patch_hadoop-config.sh_slaves.sh_branch1_no_prefix.patch, patch_hadoop-config.sh_slaves.sh_trunk.patch, patch_hadoop-config.sh_slaves.sh_trunk_no_prefix.patch, patch_slaves.sh_hadoop-1.0.3_fromtar.patch
>
>
> when the default value for HADOOP_SLAVES is changed in hadoop-env.sh the hdfs starting (with start-dfs.sh) creates secondary namenodes on all the machines in the file conf/slaves instead of conf/masters.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)