[MAPREDUCE-5466] Historyserver does not refresh the result of restarted jobs after RM restart

• Type: Sub-task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.1.1-beta
• Target Version/s: 2.1.1-beta
• Hadoop Flags: Reviewed
• Assignee: Jian He
• Reporter: Yesha Vora
• Created: 18/Aug/13 02:23
• Updated: 05/Oct/13 22:39
• Resolved: 21/Aug/13 18:19

Description

Restart RM when sort job is running and verify that the job passes successfully after RM restarts.

Once the job finishes successfully, run job status command for sort job. It shows "Job state =FAILED". Job history server does not update the result for the job which restarted after RM restart.

hadoop job -status job_1375923346354_0003
13/08/08 01:24:13 INFO mapred.ClientServiceDelegate: Application state is completed. FinalApplicationStatus=SUCCEEDED. Redirecting to job history server

Job: job_1375923346354_0003
Job File: hdfs://host1:port1/history/done/2013/08/08/000000/job_1375923346354_0003_conf.xml
Job Tracking URL : http://historyserver:port2/jobhistory/job/job_1375923346354_0003
Uber job : false
Number of maps: 80
Number of reduces: 1
map() completion: 0.0
reduce() completion: 0.0
Job state: FAILED
retired: false
reason for failure: There are no failed tasks for the job. Job is failed due to some other reason and reason can be found in the logs.
Counters not available. Job is retired.

Issue Links

• duplicates: MAPREDUCE-5401 Succeeded Job details displayed as Error In JobHistoryServer UI when RM issues Reboot to 1st app master.
• is related to: YARN-128 [Umbrella] RM Restart Phase 1: State storage and non-work-preserving recovery