[jira] [Commented] (HDFS-3284) bootstrapStandby fails in secure cluster
[ https://issues.apache.org/jira/browse/HDFS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255572#comment-13255572 ] Hudson commented on HDFS-3284: -- Integrated in Hadoop-Mapreduce-trunk #1052 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1052/]) HDFS-3284. bootstrapStandby fails in secure cluster. Contributed by Todd Lipcon. (Revision 1326813) Result = FAILURE todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1326813 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/BootstrapStandby.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/DFSHAAdmin.java > bootstrapStandby fails in secure cluster > > > Key: HDFS-3284 > URL: https://issues.apache.org/jira/browse/HDFS-3284 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, security >Affects Versions: 2.0.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 2.0.0 > > Attachments: hdfs-3284.txt, hdfs-3284.txt > > > HDFS-3247 improved bootstrapStandby to check if the other NN is in active > state before trying to bootstrap. But, it forgot to set up the kerberos > principals in the config before doing so. So, bootstrapStandby now fails with > "Failed to specify server's Kerberos principal name" in a secure cluster. > (Credit to Stephen Chu for finding this) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-3284) bootstrapStandby fails in secure cluster
[ https://issues.apache.org/jira/browse/HDFS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255532#comment-13255532 ] Hudson commented on HDFS-3284: -- Integrated in Hadoop-Hdfs-trunk #1017 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1017/]) HDFS-3284. bootstrapStandby fails in secure cluster. Contributed by Todd Lipcon. (Revision 1326813) Result = FAILURE todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1326813 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/BootstrapStandby.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/DFSHAAdmin.java > bootstrapStandby fails in secure cluster > > > Key: HDFS-3284 > URL: https://issues.apache.org/jira/browse/HDFS-3284 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, security >Affects Versions: 2.0.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 2.0.0 > > Attachments: hdfs-3284.txt, hdfs-3284.txt > > > HDFS-3247 improved bootstrapStandby to check if the other NN is in active > state before trying to bootstrap. But, it forgot to set up the kerberos > principals in the config before doing so. So, bootstrapStandby now fails with > "Failed to specify server's Kerberos principal name" in a secure cluster. > (Credit to Stephen Chu for finding this) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-3284) bootstrapStandby fails in secure cluster
[ https://issues.apache.org/jira/browse/HDFS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255171#comment-13255171 ] Hudson commented on HDFS-3284: -- Integrated in Hadoop-Mapreduce-trunk-Commit #2096 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2096/]) HDFS-3284. bootstrapStandby fails in secure cluster. Contributed by Todd Lipcon. (Revision 1326813) Result = ABORTED todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1326813 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/BootstrapStandby.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/DFSHAAdmin.java > bootstrapStandby fails in secure cluster > > > Key: HDFS-3284 > URL: https://issues.apache.org/jira/browse/HDFS-3284 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, security >Affects Versions: 2.0.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 2.0.0 > > Attachments: hdfs-3284.txt, hdfs-3284.txt > > > HDFS-3247 improved bootstrapStandby to check if the other NN is in active > state before trying to bootstrap. But, it forgot to set up the kerberos > principals in the config before doing so. So, bootstrapStandby now fails with > "Failed to specify server's Kerberos principal name" in a secure cluster. > (Credit to Stephen Chu for finding this) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-3284) bootstrapStandby fails in secure cluster
[ https://issues.apache.org/jira/browse/HDFS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255118#comment-13255118 ] Hudson commented on HDFS-3284: -- Integrated in Hadoop-Hdfs-trunk-Commit #2155 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2155/]) HDFS-3284. bootstrapStandby fails in secure cluster. Contributed by Todd Lipcon. (Revision 1326813) Result = SUCCESS todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1326813 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/BootstrapStandby.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/DFSHAAdmin.java > bootstrapStandby fails in secure cluster > > > Key: HDFS-3284 > URL: https://issues.apache.org/jira/browse/HDFS-3284 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, security >Affects Versions: 2.0.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 2.0.0 > > Attachments: hdfs-3284.txt, hdfs-3284.txt > > > HDFS-3247 improved bootstrapStandby to check if the other NN is in active > state before trying to bootstrap. But, it forgot to set up the kerberos > principals in the config before doing so. So, bootstrapStandby now fails with > "Failed to specify server's Kerberos principal name" in a secure cluster. > (Credit to Stephen Chu for finding this) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-3284) bootstrapStandby fails in secure cluster
[ https://issues.apache.org/jira/browse/HDFS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255117#comment-13255117 ] Hudson commented on HDFS-3284: -- Integrated in Hadoop-Common-trunk-Commit #2082 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2082/]) HDFS-3284. bootstrapStandby fails in secure cluster. Contributed by Todd Lipcon. (Revision 1326813) Result = SUCCESS todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1326813 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/BootstrapStandby.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/DFSHAAdmin.java > bootstrapStandby fails in secure cluster > > > Key: HDFS-3284 > URL: https://issues.apache.org/jira/browse/HDFS-3284 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, security >Affects Versions: 2.0.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Fix For: 2.0.0 > > Attachments: hdfs-3284.txt, hdfs-3284.txt > > > HDFS-3247 improved bootstrapStandby to check if the other NN is in active > state before trying to bootstrap. But, it forgot to set up the kerberos > principals in the config before doing so. So, bootstrapStandby now fails with > "Failed to specify server's Kerberos principal name" in a secure cluster. > (Credit to Stephen Chu for finding this) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-3284) bootstrapStandby fails in secure cluster
[ https://issues.apache.org/jira/browse/HDFS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255103#comment-13255103 ] Aaron T. Myers commented on HDFS-3284: -- +1, the updated patch looks good to me. Thanks a lot for taking care of this, Todd. > bootstrapStandby fails in secure cluster > > > Key: HDFS-3284 > URL: https://issues.apache.org/jira/browse/HDFS-3284 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, security >Affects Versions: 2.0.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Attachments: hdfs-3284.txt, hdfs-3284.txt > > > HDFS-3247 improved bootstrapStandby to check if the other NN is in active > state before trying to bootstrap. But, it forgot to set up the kerberos > principals in the config before doing so. So, bootstrapStandby now fails with > "Failed to specify server's Kerberos principal name" in a secure cluster. > (Credit to Stephen Chu for finding this) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-3284) bootstrapStandby fails in secure cluster
[ https://issues.apache.org/jira/browse/HDFS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255101#comment-13255101 ] Todd Lipcon commented on HDFS-3284: --- The test failure is unrelated (this patch doesn't touch that area of the code) > bootstrapStandby fails in secure cluster > > > Key: HDFS-3284 > URL: https://issues.apache.org/jira/browse/HDFS-3284 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, security >Affects Versions: 2.0.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Attachments: hdfs-3284.txt, hdfs-3284.txt > > > HDFS-3247 improved bootstrapStandby to check if the other NN is in active > state before trying to bootstrap. But, it forgot to set up the kerberos > principals in the config before doing so. So, bootstrapStandby now fails with > "Failed to specify server's Kerberos principal name" in a secure cluster. > (Credit to Stephen Chu for finding this) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-3284) bootstrapStandby fails in secure cluster
[ https://issues.apache.org/jira/browse/HDFS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255098#comment-13255098 ] Hadoop QA commented on HDFS-3284: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12522849/hdfs-3284.txt 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 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +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: org.apache.hadoop.hdfs.server.namenode.TestListCorruptFileBlocks +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2282//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2282//console This message is automatically generated. > bootstrapStandby fails in secure cluster > > > Key: HDFS-3284 > URL: https://issues.apache.org/jira/browse/HDFS-3284 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, security >Affects Versions: 2.0.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Attachments: hdfs-3284.txt, hdfs-3284.txt > > > HDFS-3247 improved bootstrapStandby to check if the other NN is in active > state before trying to bootstrap. But, it forgot to set up the kerberos > principals in the config before doing so. So, bootstrapStandby now fails with > "Failed to specify server's Kerberos principal name" in a secure cluster. > (Credit to Stephen Chu for finding this) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-3284) bootstrapStandby fails in secure cluster
[ https://issues.apache.org/jira/browse/HDFS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254934#comment-13254934 ] Todd Lipcon commented on HDFS-3284: --- ah, the addSecurityConfiguration function is only on the auto-HA branch. Let me pull that into this patch as well. > bootstrapStandby fails in secure cluster > > > Key: HDFS-3284 > URL: https://issues.apache.org/jira/browse/HDFS-3284 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, security >Affects Versions: 2.0.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Attachments: hdfs-3284.txt > > > HDFS-3247 improved bootstrapStandby to check if the other NN is in active > state before trying to bootstrap. But, it forgot to set up the kerberos > principals in the config before doing so. So, bootstrapStandby now fails with > "Failed to specify server's Kerberos principal name" in a secure cluster. > (Credit to Stephen Chu for finding this) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-3284) bootstrapStandby fails in secure cluster
[ https://issues.apache.org/jira/browse/HDFS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254930#comment-13254930 ] Hadoop QA commented on HDFS-3284: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12522829/hdfs-3284.txt 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 javadoc. The javadoc tool did not generate any warning messages. -1 javac. The patch appears to cause tar ant target to fail. +1 eclipse:eclipse. The patch built with eclipse:eclipse. -1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail. +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 . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2280//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2280//console This message is automatically generated. > bootstrapStandby fails in secure cluster > > > Key: HDFS-3284 > URL: https://issues.apache.org/jira/browse/HDFS-3284 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, security >Affects Versions: 2.0.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Attachments: hdfs-3284.txt > > > HDFS-3247 improved bootstrapStandby to check if the other NN is in active > state before trying to bootstrap. But, it forgot to set up the kerberos > principals in the config before doing so. So, bootstrapStandby now fails with > "Failed to specify server's Kerberos principal name" in a secure cluster. > (Credit to Stephen Chu for finding this) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-3284) bootstrapStandby fails in secure cluster
[ https://issues.apache.org/jira/browse/HDFS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254906#comment-13254906 ] Aaron T. Myers commented on HDFS-3284: -- +1, the patch looks good to me. > bootstrapStandby fails in secure cluster > > > Key: HDFS-3284 > URL: https://issues.apache.org/jira/browse/HDFS-3284 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, security >Affects Versions: 2.0.0 >Reporter: Todd Lipcon >Assignee: Todd Lipcon >Priority: Minor > Attachments: hdfs-3284.txt > > > HDFS-3247 improved bootstrapStandby to check if the other NN is in active > state before trying to bootstrap. But, it forgot to set up the kerberos > principals in the config before doing so. So, bootstrapStandby now fails with > "Failed to specify server's Kerberos principal name" in a secure cluster. > (Credit to Stephen Chu for finding this) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira