[jira] [Resolved] (MAPREDUCE-127) Task trackers don't register with the job tracker until after they clean out their working directory

["Harsh J (Resolved) (JIRA)" <ji...@apache.org>]

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

Harsh J resolved MAPREDUCE-127.
-------------------------------

    Resolution: Invalid

Should we register before we clean then? Frankly I've not seen this slow startups recently, even with several of our users running huge loads of tasks it never has shown up given that we keep it clean along the way.

Do reopen if this is still an issue. I do not think it is anymore, and has gone stale.
                
> Task trackers don't register with the job tracker until after they clean out their working directory
> ----------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-127
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-127
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>
> When TaskTrackers are started, they immediately start deleting their working directory, which can take 30+ minutes. Unfortunately, that means they don't register themselves with the JobTracker for a long time, so it looks like the cluster is "missing".

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