hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8767) secondary namenode on slave machines
Date Thu, 06 Sep 2012 18:37:07 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449915#comment-13449915

Arpit Gupta commented on HADOOP-8767:


I checked trunk and it looks like the same problem exists in trunk where we source the hadoop-env.sh
after reading the command line arguments. So the same fixes should apply there as well. Could
you generate a patch for trunk also.

For hadoop 1.0.3 we need to create the patch for branch-1 and that will be ported to branch-1.1
and branch-1.0 so the future 1.x releases can pick up the fix.
> 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
>            Priority: Minor
>             Fix For: 1.0.3
>         Attachments: patch_hadoop-config.sh_hadoop-1.0.3_fromtar.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

View raw message