[
https://issues.apache.org/jira/browse/HADOOP-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549514
]
Doug Cutting commented on HADOOP-2375:
--------------------------------------
If the task has more to do, shouldn't it wait to declare itself done? Or
perhaps we should introduce a new task status, "exiting" or somesuch, which
means that the output is complete but the jvm hasn't exited and hence the slot
is not yet free. If a task hangs after completing it's output but before
exiting, then the tasktracker should still kill it, but the jobtracker should
not reschedule it, right?
> Task tracker should wait for the process to exit before declaring the task
> successful or failed.
> ------------------------------------------------------------------------------------------------
>
> Key: HADOOP-2375
> URL: https://issues.apache.org/jira/browse/HADOOP-2375
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Reporter: Owen O'Malley
>
> Currently when a task declares it is done, the status in the task tracker is
> changed immediately. Instead it should wait for the subprocess to actually be
> done before it moves to one of the final states. This lead to a race
> condition where the task was still generating log data after the job tracker
> had reported the task as done.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
