[ 
https://issues.apache.org/jira/browse/HADOOP-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466425
 ] 

Arun C Murthy commented on HADOOP-912:
--------------------------------------

I've fixed org.apache.hadoop.mapred.TaskTracker.isIdle() to check if there are 
tasks waiting to be cleaned-up; what do you guys think of this approach - this 
is 'correct' according to the existing documentation of TaskTracker.isIdle(); 
however it means that TaskTracker.offerService() now waits for cleanup to 
complete before asking the JobTracker for new tasks (which is what the comment 
in offerService() is explicit about too)...

In all, this is a fix for TaskTracker.isIdle() - thoughts?


> TestMiniMRWithDFS fails sporadically
> ------------------------------------
>
>                 Key: HADOOP-912
>                 URL: https://issues.apache.org/jira/browse/HADOOP-912
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.10.1
>            Reporter: Nigel Daley
>         Assigned To: Arun C Murthy
>         Attachments: HADOOP-912_20070122.patch
>
>
> TestMiniMRWithDFS fails sporadically with the following error:
> junit.framework.AssertionFailedError: Spurious directory task_0001_m_000008_0 
> found in 
> C:\hudson\workspace\Hadoop-WindowsSmokeTest\trunk\build\test\mapred\local\50068_0
>       at 
> org.apache.hadoop.mapred.TestMiniMRWithDFS.checkTaskDirectories(TestMiniMRWithDFS.java:128)
>       at 
> org.apache.hadoop.mapred.TestMiniMRWithDFS.testWithDFS(TestMiniMRWithDFS.java:163)
> This tests checks that all mapred.local.dirs have been cleaned up after 
> running a mapred job on MiniMRCluster.  Effectively, this tests waits for 
> TaskTracker.isIdle() to return true before checking the dirs have been 
> cleaned up.  I believe that HADOOP-639 reordered the cleanup code so that 
> isIdle() will return true before the directory cleanup is complete.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to