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

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.6.1, 2.8.0, 2.7.1, 3.0.0-alpha1
• Component/s: mr-am
• Labels: 2.6.1-candidate
• Target Version/s: 2.7.1
• Hadoop Flags: Reviewed
• Assignee: Jason Darrell Lowe
• Reporter: Jason Darrell Lowe
• Created: 21/Apr/15 19:56
• Updated: 06/Jan/17 00:42
• Resolved: 27/Apr/15 22:01

Description

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.

Issue Links

• relates to: MAPREDUCE-6230 MR AM does not survive RM restart if RM activated a new AMRM secret key