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 "Hong Tang (JIRA)" <ji...@apache.org> on 2010/08/05 11:04:17 UTC
[jira] Commented: (MAPREDUCE-1253) Making Mumak work with
Capacity-Scheduler
[ https://issues.apache.org/jira/browse/MAPREDUCE-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895621#action_12895621 ]
Hong Tang commented on MAPREDUCE-1253:
--------------------------------------
Both test-patch and mumak unit tests pass on my local machine (I forgot to copy the console output of test-patch results).
{noformat}
test:
[echo] contrib: mumak
[delete] Deleting directory /grid/0/htang/hadoop-mapreduce/build/contrib/mumak/test/logs
[mkdir] Created dir: /grid/0/htang/hadoop-mapreduce/build/contrib/mumak/test/logs
[junit] WARNING: multiple versions of ant detected in path for junit
[junit] jar:file:/homes/htang/installed/ant/lib/ant.jar!/org/apache/tools/ant/Project.class
[junit] and jar:file:/homes/htang/.ivy2/cache/ant/ant/jars/ant-1.6.5.jar!/org/apache/tools/ant/Project.class
[junit] Running org.apache.hadoop.mapred.TestRemoveIpsFromLoggedNetworkTopology
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.586 sec
[junit] Running org.apache.hadoop.mapred.TestSimulatorDeterministicReplay
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 38.469 sec
[junit] Running org.apache.hadoop.mapred.TestSimulatorEndToEnd
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 107.055 sec
[junit] Running org.apache.hadoop.mapred.TestSimulatorEngine
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.162 sec
[junit] Running org.apache.hadoop.mapred.TestSimulatorEventQueue
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.02 sec
[junit] Running org.apache.hadoop.mapred.TestSimulatorJobClient
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.063 sec
[junit] Running org.apache.hadoop.mapred.TestSimulatorJobTracker
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.123 sec
[junit] Running org.apache.hadoop.mapred.TestSimulatorSerialJobSubmission
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 139.603 sec
[junit] Running org.apache.hadoop.mapred.TestSimulatorStressJobSubmission
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 100.492 sec
[junit] Running org.apache.hadoop.mapred.TestSimulatorTaskTracker
[junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 0.397 sec
{noformat}
> 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
> Attachments: MAPREDUCE-1253-20100406.patch, MAPREDUCE-1253-20100726-2.patch, MAPREDUCE-1253-20100804.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.
-
You can reply to this email to add a comment to the issue online.