You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Vinod Kumar Vavilapalli (Created) (JIRA)" <ji...@apache.org> on 2011/11/03 14:47:32 UTC

[jira] [Created] (MAPREDUCE-3340) Deprecate Job.setJobSetupCleanupNeeded()

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
             Fix For: 0.23.1


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 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