[
https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HADOOP-8767.
-------------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.0.3)
(was: site)
3.0.0
1.2.0
Hadoop Flags: Reviewed
+1 for the patch. Thank you Giovanni for reporting and fixing the issue. Thank
you Arpit for the review.
> 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, 3.0.0
>
> Attachments: patch_hadoop-config.sh_hadoop-1.0.3_fromtar.patch,
> patch_hadoop-config.sh_slaves.sh_branch1_no_prefix.patch,
> patch_hadoop-config.sh_slaves.sh_branch1.patch,
> patch_hadoop-config.sh_slaves.sh_trunk_no_prefix.patch,
> patch_hadoop-config.sh_slaves.sh_trunk.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
