[
https://issues.apache.org/jira/browse/MAPREDUCE-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated MAPREDUCE-3340:
----------------------------------------
Fix Version/s: (was: 0.24.0)
> Deprecate Job.setJobSetupCleanupNeeded()
> ----------------------------------------
>
> Key: MAPREDUCE-3340
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3340
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> We should deprecate the setJobSetupCleanupNeeded() API. It was originally
> added for performance reasons to avoid launching new JVMs altogether for
> job-setup and job-cleanup. With Yarn and MRAppMaster, setup and cleanup are
> run inside the AM itself and so nothing much can be gained by making them
> optional.
> Before 0.23, we could disable set up and cleanup, yet obtain the output when
> using FileOutputCommitter in the job-output directory. But post 0.23.0, that
> won't be the case because of the nested temporary directories to support AM
> recoverability. So it makes sense to *not* have cleanupJob optional.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
