[
https://issues.apache.org/jira/browse/MAPREDUCE-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061879#comment-15061879
]
Devaraj K commented on MAPREDUCE-4788:
--------------------------------------
I faced this issue long time back during the version 2.0.4-alpha. I don't think
it is still an issue with the changes happened over the time.
bq. Is the job history not correct on this state as well?
Yes, the job history was also showing the job state as FAILED and the task
state as KILLED but we could see the attempt for the task as succeeded.
I don't have logs for this issue since it happened some time ago.
[~brahmareddy], Can you give details or share the log for the issue you are
facing if you have anything?
> Job are marking as FAILED even if there are no failed tasks in it
> -----------------------------------------------------------------
>
> Key: MAPREDUCE-4788
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4788
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster
> Affects Versions: 2.6.0
> Reporter: Devaraj K
> Attachments: MAPREDUCE-4788.patch
>
>
> Sometimes Jobs are marking as FAILED and some the tasks are marking as KILLED
> in it.
> In MRAppMaster, JobFinishEvent is triggering and waiting for the 5000 millis.
> If any tasks final state is unknown by this time those tasks are marking as
> KILLED and Job state is marking as FAILED.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
