[
https://issues.apache.org/jira/browse/MAPREDUCE-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505767#comment-14505767
]
Robert Kanter commented on MAPREDUCE-6324:
------------------------------------------
Thanks for finding this issue and posting it; this'll be helpful for anyone
using Uber mode.
LGTM +1 on the change. It seems like this might be tricky to do, but would it
be possible to add a unit test?
> 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
> Attachments: MAPREDUCE-6324.001.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)
