[ https://issues.apache.org/jira/browse/MAPREDUCE-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516856#comment-14516856 ]
Hudson commented on MAPREDUCE-6324: ----------------------------------- FAILURE: Integrated in Hadoop-Hdfs-trunk #2109 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2109/]) MAPREDUCE-6324. Fixed MapReduce uber jobs to not fail the udpate of AM-RM tokens when they roll-over. Contributed by Jason Lowe. (vinodkv: rev 9fc32c5c4d1d5f50c605bdb0e3b13f44c86660c8) * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/local/LocalContainerAllocator.java * hadoop-mapreduce-project/CHANGES.txt * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/local/TestLocalContainerAllocator.java > Uber jobs fail to update AMRM token when it rolls over > ------------------------------------------------------ > > Key: MAPREDUCE-6324 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6324 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mr-am > Affects Versions: 2.6.0 > Reporter: Jason Lowe > Assignee: Jason Lowe > Priority: Blocker > Fix For: 2.7.1 > > Attachments: MAPREDUCE-6324.001.patch, MAPREDUCE-6324.002.patch > > > When the RM rolls a new AMRM master key the AMs are supposed to receive a new > AMRM token on subsequent heartbeats between the time when the new key is > rolled and when it is activated. This is not occurring for uber jobs. If > the connection to the RM needs to be re-established after the new key is > activated (e.g.: RM restart or network hiccup) then the uber job AM will be > unable to reconnect to the RM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)