You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Koji Noguchi (JIRA)" <ji...@apache.org> on 2011/01/31 17:49:30 UTC

[jira] Created: (MAPREDUCE-2291) TaskTracker Decommission that waits for all map(intermediate) outputs to be pulled

TaskTracker Decommission that waits for all map(intermediate) outputs to be pulled 
-----------------------------------------------------------------------------------

                 Key: MAPREDUCE-2291
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2291
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
          Components: jobtracker
            Reporter: Koji Noguchi


On our clusters, users were getting affected when ops were decommissioning a large number of TaskTracker nodes. 

Correct me if I'm wrong, but current decommission of TaskTrackers only waits for the running tasks to finish but not
the jobs where map outputs are kept on that decommissioning tasktrackers.

Any ways we can handle this better?


-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira