[YARN-1366] AM should implement Resync with the ApplicationMasterService instead of shutting down

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.5.0
• Component/s: resourcemanager
• Target Version/s: 2.6.0
• Hadoop Flags: Reviewed
• Assignee: Rohith Sharma K S
• Reporter: Bikas Saha
• Created: 30/Oct/13 06:39
• Updated: 13/Oct/15 08:51
• Resolved: 09/Jul/14 18:29

Description

The ApplicationMasterService currently sends a resync response to which the AM responds by shutting down. The AM behavior is expected to change to calling resyncing with the RM. Resync means resetting the allocate RPC sequence number to 0 and the AM should send its entire outstanding request to the RM. Note that if the AM is making its first allocate call to the RM then things should proceed like normal without needing a resync. The RM will return all containers that have completed since the RM last synced with the AM. Some container completions may be reported more than once.

Issue Links

• breaks: YARN-4251 TestAMRMClientOnRMRestart#testAMRMClientOnAMRMTokenRollOverOnRMRestart is failing
• relates to: MAPREDUCE-5910 MRAppMaster should handle Resync from RM instead of shutting down.