You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2015/04/21 21:57:00 UTC

[jira] [Created] (MAPREDUCE-6324) Uber jobs fail to update AMRM token when it rolls over

Jason Lowe created MAPREDUCE-6324:
-------------------------------------

             Summary: 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


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)