[ https://issues.apache.org/jira/browse/HADOOP-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Devaraj Das updated HADOOP-2375:

Fix Version/s: 0.20.0
Assignee: Devaraj Das

I forgot to take care of this issue in the JVM reuse patch too. In that, the JVM is explicitly killed if it is found to be idle. But it might sometimes have an unfortunate side effect to do with logs not fully flushed yet.
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 Core
Issue Type: Bug
Components: mapred
Reporter: Owen O'Malley
Assignee: Devaraj Das
Fix For: 0.20.0

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.

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
postedOct 8, '08 at 10:30a
activeOct 8, '08 at 10:30a

1 user in discussion

Devaraj Das (JIRA): 1 post



site design / logo © 2021 Grokbase