hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6324) Uber jobs fail to update AMRM token when it rolls over
Date Thu, 23 Apr 2015 23:45:41 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510086#comment-14510086

Vinod Kumar Vavilapalli commented on MAPREDUCE-6324:

Looks good to me. One nit: testAllocResponseId is not really validating that responseIDs are

> 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, 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

View raw message