[jira] [Commented] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key
[ https://issues.apache.org/jira/browse/MAPREDUCE-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296716#comment-14296716 ] Hudson commented on MAPREDUCE-6230: --- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #88 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/88/]) MAPREDUCE-6230. Fixed RMContainerAllocator to update the new AMRMToken service name properly. Contributed by Jason Lowe (jianhe: rev cff05bff1fe24628677d41a0d537f2c383b44faf) * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/rm/TestRMContainerAllocator.java * hadoop-mapreduce-project/CHANGES.txt * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java MR AM does not survive RM restart if RM activated a new AMRM secret key --- Key: MAPREDUCE-6230 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6230 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Reporter: Jason Lowe Assignee: Jason Lowe Priority: Blocker Fix For: 2.7.0 Attachments: MAPREDUCE-6230.001.patch A MapReduce AM will fail to reconnect to an RM that performed restart in the following scenario: # MapReduce job launched with AMRM token generated from AMRM secret X # RM rolls new AMRM secret Y and activates the new key # RM performs a work-preserving restart # MapReduce job AM now unable to connect to RM with Invalid AMRMToken exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key
[ https://issues.apache.org/jira/browse/MAPREDUCE-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296727#comment-14296727 ] Hudson commented on MAPREDUCE-6230: --- FAILURE: Integrated in Hadoop-Yarn-trunk #822 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/822/]) MAPREDUCE-6230. Fixed RMContainerAllocator to update the new AMRMToken service name properly. Contributed by Jason Lowe (jianhe: rev cff05bff1fe24628677d41a0d537f2c383b44faf) * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/rm/TestRMContainerAllocator.java * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java * hadoop-mapreduce-project/CHANGES.txt MR AM does not survive RM restart if RM activated a new AMRM secret key --- Key: MAPREDUCE-6230 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6230 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Reporter: Jason Lowe Assignee: Jason Lowe Priority: Blocker Fix For: 2.7.0 Attachments: MAPREDUCE-6230.001.patch A MapReduce AM will fail to reconnect to an RM that performed restart in the following scenario: # MapReduce job launched with AMRM token generated from AMRM secret X # RM rolls new AMRM secret Y and activates the new key # RM performs a work-preserving restart # MapReduce job AM now unable to connect to RM with Invalid AMRMToken exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key
[ https://issues.apache.org/jira/browse/MAPREDUCE-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296999#comment-14296999 ] Hudson commented on MAPREDUCE-6230: --- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2039 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2039/]) MAPREDUCE-6230. Fixed RMContainerAllocator to update the new AMRMToken service name properly. Contributed by Jason Lowe (jianhe: rev cff05bff1fe24628677d41a0d537f2c383b44faf) * hadoop-mapreduce-project/CHANGES.txt * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/rm/TestRMContainerAllocator.java * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java MR AM does not survive RM restart if RM activated a new AMRM secret key --- Key: MAPREDUCE-6230 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6230 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Reporter: Jason Lowe Assignee: Jason Lowe Priority: Blocker Fix For: 2.7.0 Attachments: MAPREDUCE-6230.001.patch A MapReduce AM will fail to reconnect to an RM that performed restart in the following scenario: # MapReduce job launched with AMRM token generated from AMRM secret X # RM rolls new AMRM secret Y and activates the new key # RM performs a work-preserving restart # MapReduce job AM now unable to connect to RM with Invalid AMRMToken exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key
[ https://issues.apache.org/jira/browse/MAPREDUCE-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296802#comment-14296802 ] Hudson commented on MAPREDUCE-6230: --- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #89 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/89/]) MAPREDUCE-6230. Fixed RMContainerAllocator to update the new AMRMToken service name properly. Contributed by Jason Lowe (jianhe: rev cff05bff1fe24628677d41a0d537f2c383b44faf) * hadoop-mapreduce-project/CHANGES.txt * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/rm/TestRMContainerAllocator.java * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java MR AM does not survive RM restart if RM activated a new AMRM secret key --- Key: MAPREDUCE-6230 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6230 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Reporter: Jason Lowe Assignee: Jason Lowe Priority: Blocker Fix For: 2.7.0 Attachments: MAPREDUCE-6230.001.patch A MapReduce AM will fail to reconnect to an RM that performed restart in the following scenario: # MapReduce job launched with AMRM token generated from AMRM secret X # RM rolls new AMRM secret Y and activates the new key # RM performs a work-preserving restart # MapReduce job AM now unable to connect to RM with Invalid AMRMToken exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key
[ https://issues.apache.org/jira/browse/MAPREDUCE-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296892#comment-14296892 ] Hudson commented on MAPREDUCE-6230: --- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #85 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/85/]) MAPREDUCE-6230. Fixed RMContainerAllocator to update the new AMRMToken service name properly. Contributed by Jason Lowe (jianhe: rev cff05bff1fe24628677d41a0d537f2c383b44faf) * hadoop-mapreduce-project/CHANGES.txt * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/rm/TestRMContainerAllocator.java * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java MR AM does not survive RM restart if RM activated a new AMRM secret key --- Key: MAPREDUCE-6230 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6230 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Reporter: Jason Lowe Assignee: Jason Lowe Priority: Blocker Fix For: 2.7.0 Attachments: MAPREDUCE-6230.001.patch A MapReduce AM will fail to reconnect to an RM that performed restart in the following scenario: # MapReduce job launched with AMRM token generated from AMRM secret X # RM rolls new AMRM secret Y and activates the new key # RM performs a work-preserving restart # MapReduce job AM now unable to connect to RM with Invalid AMRMToken exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key
[ https://issues.apache.org/jira/browse/MAPREDUCE-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296926#comment-14296926 ] Hudson commented on MAPREDUCE-6230: --- SUCCESS: Integrated in Hadoop-Hdfs-trunk #2020 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2020/]) MAPREDUCE-6230. Fixed RMContainerAllocator to update the new AMRMToken service name properly. Contributed by Jason Lowe (jianhe: rev cff05bff1fe24628677d41a0d537f2c383b44faf) * hadoop-mapreduce-project/CHANGES.txt * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/rm/TestRMContainerAllocator.java MR AM does not survive RM restart if RM activated a new AMRM secret key --- Key: MAPREDUCE-6230 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6230 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Reporter: Jason Lowe Assignee: Jason Lowe Priority: Blocker Fix For: 2.7.0 Attachments: MAPREDUCE-6230.001.patch A MapReduce AM will fail to reconnect to an RM that performed restart in the following scenario: # MapReduce job launched with AMRM token generated from AMRM secret X # RM rolls new AMRM secret Y and activates the new key # RM performs a work-preserving restart # MapReduce job AM now unable to connect to RM with Invalid AMRMToken exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key
[
https://issues.apache.org/jira/browse/MAPREDUCE-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295397#comment-14295397
]
Hadoop QA commented on MAPREDUCE-6230:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12695013/MAPREDUCE-6230.001.patch
against trunk revision 9850e15.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5126//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5126//console
This message is automatically generated.
MR AM does not survive RM restart if RM activated a new AMRM secret key
---
Key: MAPREDUCE-6230
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6230
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mr-am
Reporter: Jason Lowe
Assignee: Jason Lowe
Priority: Blocker
Attachments: MAPREDUCE-6230.001.patch
A MapReduce AM will fail to reconnect to an RM that performed restart in the
following scenario:
# MapReduce job launched with AMRM token generated from AMRM secret X
# RM rolls new AMRM secret Y and activates the new key
# RM performs a work-preserving restart
# MapReduce job AM now unable to connect to RM with Invalid AMRMToken
exception
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key
[ https://issues.apache.org/jira/browse/MAPREDUCE-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296107#comment-14296107 ] Hudson commented on MAPREDUCE-6230: --- FAILURE: Integrated in Hadoop-trunk-Commit #6954 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/6954/]) MAPREDUCE-6230. Fixed RMContainerAllocator to update the new AMRMToken service name properly. Contributed by Jason Lowe (jianhe: rev cff05bff1fe24628677d41a0d537f2c383b44faf) * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/rm/TestRMContainerAllocator.java * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java * hadoop-mapreduce-project/CHANGES.txt MR AM does not survive RM restart if RM activated a new AMRM secret key --- Key: MAPREDUCE-6230 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6230 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Reporter: Jason Lowe Assignee: Jason Lowe Priority: Blocker Fix For: 2.7.0 Attachments: MAPREDUCE-6230.001.patch A MapReduce AM will fail to reconnect to an RM that performed restart in the following scenario: # MapReduce job launched with AMRM token generated from AMRM secret X # RM rolls new AMRM secret Y and activates the new key # RM performs a work-preserving restart # MapReduce job AM now unable to connect to RM with Invalid AMRMToken exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key
[ https://issues.apache.org/jira/browse/MAPREDUCE-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296073#comment-14296073 ] Jian He commented on MAPREDUCE-6230: +1 MR AM does not survive RM restart if RM activated a new AMRM secret key --- Key: MAPREDUCE-6230 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6230 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Reporter: Jason Lowe Assignee: Jason Lowe Priority: Blocker Attachments: MAPREDUCE-6230.001.patch A MapReduce AM will fail to reconnect to an RM that performed restart in the following scenario: # MapReduce job launched with AMRM token generated from AMRM secret X # RM rolls new AMRM secret Y and activates the new key # RM performs a work-preserving restart # MapReduce job AM now unable to connect to RM with Invalid AMRMToken exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key
[ https://issues.apache.org/jira/browse/MAPREDUCE-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14293809#comment-14293809 ] Jason Lowe commented on MAPREDUCE-6230: --- There are a couple of reasons this doesn't work: 1) The token handed to the AM from the RM does not have a service set, since the RM does not know the service name being used by the client to connect to the RM. Unfortunately the RMContainerAllocator never updates the service name of the token, so it ends up not being selected by the RPC layer when reconnecting to the RM. 2) The RMContainerAllocator for some reason tries to update the login user rather than the current user when security is enabled. This ends up updating a token in the UGI that is _not_ being used by the IPC layer when reconnecting to the RM on a secure cluster. Also note that the AMRM token is mapped with an empty service name in the credentials, so if the token service is updated before adding it to the credentials we can end up with two AMRM tokens (one with an empty service key and one with a non-empty service key). So we need to be careful when adding the new token to the credentials that we will indeed be clobbering the old token, as we need to use a consistent service/alias that we cannot obtain directly from the credentials. MR AM does not survive RM restart if RM activated a new AMRM secret key --- Key: MAPREDUCE-6230 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6230 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Reporter: Jason Lowe Assignee: Jason Lowe Priority: Blocker A MapReduce AM will fail to reconnect to an RM that performed restart in the following scenario: # MapReduce job launched with AMRM token generated from AMRM secret X # RM rolls new AMRM secret Y and activates the new key # RM performs a work-preserving restart # MapReduce job AM now unable to connect to RM with Invalid AMRMToken exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
