[
https://issues.apache.org/jira/browse/MAPREDUCE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved MAPREDUCE-216.
-------------------------------
Resolution: Not A Problem
Some level of this can be achieved with the OutputCommitters today. Closing out.
> Job setup and take down on Nodes
> --------------------------------
>
> Key: MAPREDUCE-216
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-216
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Reporter: Benjamin Reed
> Assignee: Owen O'Malley
>
> It would be nice if there was a hook for doing job provisioning and cleanup
> on compute nodes. The TaskTracker implicitly knows when a job starts (a task
> for the job is received) and pollForTaskWithClosedJob() will explicitly say
> that a job is finished if a Map task has been run (If only Reduce tasks have
> run and are finished I don't think pollForTaskWithClosedJob() will return
> anything will it?), but child Tasks do not get this information.
> It would be nice if there was a hook so that programmers could do some
> provisioning when a job starts and cleanup when a job ends. Caching addresses
> some of the provisioning, but in some cases a helper daemon may need to be
> started or the results of queries need to be retrieved and having startJob(),
> finishJob() callbacks that happen exactly once for each node that runs part
> of the job would be wonderful.
--
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
