[
https://issues.apache.org/jira/browse/MAPREDUCE-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505805#comment-14505805
]
Jason Lowe commented on MAPREDUCE-6324:
---------------------------------------
Thanks for the review, Robert! Yes, this should have a unit test. Wanted to
post a version without since I was able to manually test it with an uberized
Oozie launcher job and verify it fixes the issue. I'm busy with a bunch of
other stuff right now, but I'll try to take a crack at adding a unit test later
this week.
> 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)
