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] [Updated] (MAPREDUCE-6230) MR AM does not survive RM restart if RM activated a new AMRM secret key
Date Mon, 31 Aug 2015 22:54:46 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated MAPREDUCE-6230:
-----------------------------------------------
    Fix Version/s: 2.6.1

Pulled this into 2.6.1. Ran compilation and TestRMContainerAllocator before the push. Patch
applied cleanly.

> MR AM does not survive RM restart if RM activated a new AMRM secret key
> -----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6230
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6230
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Blocker
>              Labels: 2.6.1-candidate
>             Fix For: 2.7.0, 2.6.1
>
>         Attachments: MAPREDUCE-6230.001.patch
>
>
> A MapReduce AM will fail to reconnect to an RM that performed restart in the following
scenario:
> # MapReduce job launched with AMRM token generated from AMRM secret X
> # RM rolls new AMRM secret Y and activates the new key
> # RM performs a work-preserving restart
> # MapReduce job AM now unable to connect to RM with "Invalid AMRMToken" exception



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message