hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1253) Making Mumak work with Capacity-Scheduler
Date Wed, 02 Dec 2009 04:53:20 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784627#action_12784627

Vinod K V commented on MAPREDUCE-1253:

No idea how the Mumak test code is written, but various test-cases in {{TestCapacityScheduler}}
already replace the initialization thread with a {{ControlledInitializationPoller}} for the
sake of deterministic testing. Please see {{testJobInitialization()}} if it helps.

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

View raw message