[MAPREDUCE-2692] Ensure AM Restart and Recovery-on-restart is complete

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.0
• Fix Version/s: 0.23.0
• Component/s: mrv2
• Assignee: Sharad Agarwal
• Reporter: Amol Kekre
• Created: 15/Jul/11 22:12
• Updated: 15/Nov/11 00:49
• Resolved: 31/Oct/11 04:47

Description

Need to get AM restart and the subsequent recover after restart to work

Sub-Tasks

• [MR-279] Design and implement MR Application Master recovery: Closed
• MR-279: AM restart does not work after RM refactor: Closed
• [MR-279] OutputCommitter changes for MR Application Master recovery: Closed
• MR-279: Need to retrieve shuffle port number on ApplicationMaster restart: Closed
• Port MAPREDUCE-2702 to old mapred api: Closed
• AM fails to restart when first AM is killed: Closed
• Recovery of MR AMs with reduces fails the subsequent generation of the job: Closed
• When AM restarts, client keeps reconnecting to the new AM and prints a lots of logs.: Closed
• AMRecovery should pick completed task form partial JobHistory files: Closed
• AppMaster recovery for Medium to large jobs take long time: Closed
• If an MR AM dies twice it looks like the process freezes: Closed
• Restarted+Recovered AM hangs in some corner cases: Closed