[MAPREDUCE-4235] Killing app can lead to inconsistent app status between RM and HS

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 0.23.3
• Component/s: mrv2
• Assignee: Unassigned
• Reporter: Jason Darrell Lowe
• Created: 08/May/12 22:36
• Updated: 24/May/13 15:23
• Resolved: 24/May/13 15:23

Description

If a client tries to kill an application that is about to complete, the application states between the ResourceManager's web UI and the history server can be inconsistent. When the problem occurs, the ResourceManager shows the Status/FinalStatus as KILLED/KILLED and the history link will redirect to a broken link. The history link still references the ApplicationMaster which is now missing. The history server entry will show the application state as SUCCEEDED.