hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "rahul k singh (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1408) Allow customization of job submission policies
Date Tue, 16 Feb 2010 05:50:29 GMT

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

rahul k singh updated MAPREDUCE-1408:

    Attachment: 1408-2.patch

Implemented all the points mentioned above except:
The JobMonitor::process method can probably be removed, since it doesn't do any meaningful
work (the instance is instead passed to the downstream StatsCollector, which does). The monitor
is then only responsible for determining when the job is done, not its outcome The unit test
can subclass the downstream component instead of subclassing JobMonitor 

The above is not done , due to time constraints and also extend Statistics is taking time.
Will open the new jira where we will remove the process method.

For the question:
If a job fails submission in serial mode, wil the JobFactory be woken up?

> Allow customization of job submission policies
> ----------------------------------------------
>                 Key: MAPREDUCE-1408
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1408
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/gridmix
>            Reporter: rahul k singh
>         Attachments: 1408-1.patch, 1408-2.patch
> Currently, gridmix3 replay job submission faithfully. For evaluation purposes, it would
be great if we can support other job submission policies such as sequential job submission,
or stress job submission.

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

View raw message