hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5785) The job setup and cleanup tasks should be optional
Date Fri, 05 Jun 2009 07:56:07 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716530#action_12716530
] 

Amar Kamat commented on HADOOP-5785:
------------------------------------

Some comments on JobInProgress :
1. remove JobContext. construct during initTasks.
2. Move setup/cleanup tasks initialization to different method
3. introduce methods setupInline/cleanupInline to do setup/cleanup inline in initTasks and
garbageCollect.
4. Remove jobSetupCleanupNeeded guards from canLaunchJobCleanup/SetupTask() methods. And Use
them in completedTask whenever maps/reduces complete.
5. add an api to FileoutputCommitter to give temp dir.


> The job setup and cleanup tasks should be optional
> --------------------------------------------------
>
>                 Key: HADOOP-5785
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5785
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: Owen O'Malley
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.21.0
>
>         Attachments: patch-5785-1.txt, patch-5785.txt
>
>
> For jobs that require low latency and do not require setup or cleanup tasks for the job,
it should be possible to turn them off for that job.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message