Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <21848138.168131280960659706.JavaMail.jira@thor>
Date: Wed, 4 Aug 2010 18:24:19 -0400 (EDT)
From: "Hong Tang (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-1253) Making Mumak work with
 Capacity-Scheduler
In-Reply-To: <1023403449.1259630484817.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hong Tang updated MAPREDUCE-1253:
---------------------------------

    Status: Open  (was: Patch Available)

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