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 "giovanni delussu (JIRA)" <ji...@apache.org> on 2012/09/05 14:24:08 UTC
[jira] [Created] (HADOOP-8767) secondary namenode on slave machines
giovanni delussu created HADOOP-8767:
----------------------------------------
Summary: 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
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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448771#comment-13448771 ]
Hadoop QA commented on HADOOP-8767:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12543859/patch_slaves.sh_hadoop-1.0.3_fromtar.patch
against trunk revision .
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1405//console
This message is automatically generated.
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Andy Isaacson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450882#comment-13450882 ]
Andy Isaacson commented on HADOOP-8767:
---------------------------------------
bq. could you generate the patch using git --no-prefix, otherwiese i have to provide which file to patch.
You can apply this patch with {{patch -p1}}.
{code}
diff --git a/bin/hadoop-config.sh b/bin/hadoop-config.sh
index c23cbcf..073a5fe 100644
--- a/bin/hadoop-config.sh
+++ b/bin/hadoop-config.sh
% cd branch-1
% patch -p1 < /tmp/patch_hadoop-config.sh_slaves.sh_branch1.patch
patching file bin/hadoop-config.sh
patching file bin/slaves.sh
%
{code}
Using {{--no-prefix}} makes the patch less useful to others. :)
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450890#comment-13450890 ]
Arpit Gupta commented on HADOOP-8767:
-------------------------------------
@Andy
thanks for the info. However i was just following what we recommend to users on our wiki http://wiki.apache.org/hadoop/GitAndHadoop
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453345#comment-13453345 ]
Hudson commented on HADOOP-8767:
--------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #2742 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2742/])
HADOOP-8767. Secondary namenode is started on slave nodes instead of master nodes. Contributed by Giovanni Delussu. (Revision 1383560)
Result = FAILURE
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1383560
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/slaves.sh
> 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
[jira] [Assigned] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Suresh Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Srinivas reassigned HADOOP-8767:
---------------------------------------
Assignee: giovanni delussu
Giovanni, I added you as a Hadoop Common contributor and assigned the jira to you.
> 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: site, 1.0.3
>
> 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
[jira] [Updated] (HADOOP-8767) secondary namenode on slave machines
Posted by "giovanni delussu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
giovanni delussu updated HADOOP-8767:
-------------------------------------
Status: Patch Available (was: Open)
> 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
>
> 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
[jira] [Updated] (HADOOP-8767) secondary namenode on slave machines
Posted by "Suresh Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Srinivas updated HADOOP-8767:
------------------------------------
Status: In Progress (was: Patch Available)
> 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: site, 1.0.3
>
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454009#comment-13454009 ]
Hudson commented on HADOOP-8767:
--------------------------------
Integrated in Hadoop-Mapreduce-trunk #1194 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1194/])
HADOOP-8767. Secondary namenode is started on slave nodes instead of master nodes. Contributed by Giovanni Delussu. (Revision 1383560)
Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1383560
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/slaves.sh
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453316#comment-13453316 ]
Hudson commented on HADOOP-8767:
--------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #2781 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2781/])
HADOOP-8767. Secondary namenode is started on slave nodes instead of master nodes. Contributed by Giovanni Delussu. (Revision 1383560)
Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1383560
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/slaves.sh
> 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: site, 1.0.3
>
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "giovanni delussu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450506#comment-13450506 ]
giovanni delussu commented on HADOOP-8767:
------------------------------------------
[~arpitgupta] I checked again and found that in branch-1 I need to move the setting of the HOSTLIST variable because when slaves.sh calls hadoop-config.sh it hasn't the --hosts attached so hadoop-config.sh sets HADOOP_SLAVES (by calling hadoop-env.sh) to the slaves file instead of the masters.
> 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_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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450482#comment-13450482 ]
Hadoop QA commented on HADOOP-8767:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12544187/patch_hadoop-config.sh_slaves.sh_trunk.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these unit tests in hadoop-common-project/hadoop-common:
org.apache.hadoop.ha.TestZKFailoverController
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1422//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1422//console
This message is automatically generated.
> 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_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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453315#comment-13453315 ]
Hudson commented on HADOOP-8767:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #2718 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2718/])
HADOOP-8767. Secondary namenode is started on slave nodes instead of master nodes. Contributed by Giovanni Delussu. (Revision 1383560)
Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1383560
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/slaves.sh
> 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: site, 1.0.3
>
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450510#comment-13450510 ]
Hadoop QA commented on HADOOP-8767:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12544197/patch_hadoop-config.sh_slaves.sh_branch1.patch
against trunk revision .
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1423//console
This message is automatically generated.
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453257#comment-13453257 ]
Arpit Gupta commented on HADOOP-8767:
-------------------------------------
+1 the latest changes look good to go.
> 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_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
[jira] [Updated] (HADOOP-8767) secondary namenode on slave machines
Posted by "giovanni delussu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
giovanni delussu updated HADOOP-8767:
-------------------------------------
Attachment: patch_slaves.sh_hadoop-1.0.3_fromtar.patch
patch_hadoop-config.sh_hadoop-1.0.3_fromtar.patch
patch for tar version hadoop-1.0.3.tar.gz
file patched are:
hadoop-config.sh
slaves.sh
> 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
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ 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:
-------------------------------------
@Giovanni
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
[jira] [Updated] (HADOOP-8767) secondary namenode on slave machines
Posted by "giovanni delussu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
giovanni delussu updated HADOOP-8767:
-------------------------------------
Attachment: patch_hadoop-config.sh_slaves.sh_trunk_no_prefix.patch
patch_hadoop-config.sh_slaves.sh_branch1_no_prefix.patch
patch with --no-prefix
> 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_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
[jira] [Updated] (HADOOP-8767) secondary namenode on slave machines
Posted by "giovanni delussu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
giovanni delussu updated HADOOP-8767:
-------------------------------------
Fix Version/s: 1.0.3
Status: Patch Available (was: Open)
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "giovanni delussu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452762#comment-13452762 ]
giovanni delussu commented on HADOOP-8767:
------------------------------------------
ops. plural=> patches with --no-prefix flag
> 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_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
[jira] [Updated] (HADOOP-8767) secondary namenode on slave machines
Posted by "giovanni delussu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
giovanni delussu updated HADOOP-8767:
-------------------------------------
Attachment: patch_hadoop-config.sh_slaves.sh_branch1.patch
patch for branch1
> 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
[jira] [Updated] (HADOOP-8767) secondary namenode on slave machines
Posted by "giovanni delussu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
giovanni delussu updated HADOOP-8767:
-------------------------------------
Fix Version/s: site
> 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_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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "giovanni delussu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449436#comment-13449436 ]
giovanni delussu commented on HADOOP-8767:
------------------------------------------
About the format: I cloned with git the trunk repository but the two files I'm proposing to change are different. So this is not a patch for the trunk. This is only a patch for the hadoop-1.0.3.tar.gz version. What should I do? Create a git with hadoop-1.0.3.tar.gz and then after the change publish the "git diff"?
about the comments: 1 is already the way I modified hadoop-config.sh
2 I thought in slaves.sh the sourcing of hadoop-env.sh could serve to other stuff but if this is not the case I agree that we should remove it.
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450898#comment-13450898 ]
Arpit Gupta commented on HADOOP-8767:
-------------------------------------
also --no-prefix only removes the "a/.. b/..." so not sure how it will be less useful.
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453962#comment-13453962 ]
Hudson commented on HADOOP-8767:
--------------------------------
Integrated in Hadoop-Hdfs-trunk #1163 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1163/])
HADOOP-8767. Secondary namenode is started on slave nodes instead of master nodes. Contributed by Giovanni Delussu. (Revision 1383560)
Result = FAILURE
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1383560
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/slaves.sh
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Arpit Gupta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448958#comment-13448958 ]
Arpit Gupta commented on HADOOP-8767:
-------------------------------------
Patch does not seem to be correctly formatted. For details on take a look at http://wiki.apache.org/hadoop/HowToContribute or if you use git then http://wiki.apache.org/hadoop/GitAndHadoop
A few comments on your patch.
Rather than assigning HOSTLIST after hadoop-env.sh is sourced we should do the following
1. in hadoop-config.sh source the hadoop-env.sh before additional parameters are processed such as --hosts. This way if you specify the hosts at command line they will get set appropriately. This will help as in start-dfs.sh the secondary namenode is being started as
{code}
"$bin"/hadoop-daemons.sh --config $HADOOP_CONF_DIR --hosts masters start secondarynamenode
{code}
2. in slaves.sh remove the source of hadoop-env.sh as it has already been sourced by hadoop-config.sh. Thus the assignment of HADOOP_SLAVES done by hadoop-config.sh will be available rather than being overwritten by hadoop-env.sh
> 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
[jira] [Commented] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452798#comment-13452798 ]
Hadoop QA commented on HADOOP-8767:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12544601/patch_hadoop-config.sh_slaves.sh_trunk_no_prefix.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in hadoop-common-project/hadoop-common.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1435//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1435//console
This message is automatically generated.
> 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_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
[jira] [Resolved] (HADOOP-8767) secondary namenode on slave
machines
Posted by "Suresh Srinivas (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (HADOOP-8767) secondary namenode on slave machines
Posted by "giovanni delussu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
giovanni delussu updated HADOOP-8767:
-------------------------------------
Attachment: patch_hadoop-config.sh_slaves.sh_trunk.patch
patch of the secondary namenode issue for the trunk
> 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_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
[jira] [Updated] (HADOOP-8767) secondary namenode on slave machines
Posted by "giovanni delussu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
giovanni delussu updated HADOOP-8767:
-------------------------------------
Status: Open (was: Patch Available)
> 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
>
> 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