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 Fri, 07 Sep 2012 18:25:07 GMT

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

Arpit Gupta commented on HADOOP-8767:

could you generate the patch using git --no-prefix, otherwiese i have to provide which file
to patch.

Also for the patches the naming convention is something like HADOOP-8767.patch for trunk and
HADOOP-8767.branch-1.patch for branch-1

Also good catch on the branch-1 changes.
> 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: site, 1.0.3
>         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_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

View raw message