[
https://issues.apache.org/jira/browse/MAPREDUCE-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated MAPREDUCE-6324:
----------------------------------
Attachment: MAPREDUCE-6324.001.patch
Patch that fixes two problems with the LocalContainerAllocator used for uber
jobs:
# The last response ID was not being updated, so the RM was always re-sending
the first response it ever sent and thus the job was never receiving an updated
AMRM token
# Any updated AMRM token in the response was being ignored
> 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)
