You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Anirban Dasgupta (JIRA)" <ji...@apache.org> on 2010/04/12 22:54:51 UTC
[jira] Updated: (MAPREDUCE-1253) Making Mumak work with
Capacity-Scheduler
[ https://issues.apache.org/jira/browse/MAPREDUCE-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anirban Dasgupta updated MAPREDUCE-1253:
----------------------------------------
Attachment: MAPREDUCE-1253-20100406.patch
I am attaching a partial patch at this point. In offline testing I am observing some javadoc and findbugs warnings. It seems that the main build.xml has to be changed to remove these.
> Making Mumak work with Capacity-Scheduler
> -----------------------------------------
>
> Key: MAPREDUCE-1253
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1253
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/mumak
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Anirban Dasgupta
> Assignee: Anirban Dasgupta
> Priority: Minor
> Attachments: MAPREDUCE-1253-20100406.patch
>
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> In order to make the capacity-scheduler work in the mumak simulation environment, we have to replace the job-initialization threads of the capacity scheduler with classes that perform event-based initialization. We propose to use aspectj to disable the threads of the JobInitializationPoller class used by the Capacity Scheduler, and then perform the corresponding initialization tasks through a simulation job-initialization class that receives periodic wake-up calls from the simulator engine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira