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 "Patrick Wendell (Commented) (JIRA)" <ji...@apache.org> on 2011/12/27 02:08:30 UTC

[jira] [Commented] (MAPREDUCE-3602) Add Preemption to MR2 Fair Scheduler

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

Patrick Wendell commented on MAPREDUCE-3602:
--------------------------------------------

The MR2 node update API already has hooks for the RM to tell the NM to release containers. Are there any problems using this method to preempt containers? I.e. will application masters handle unexpected container disruption gracefully or are there other considerations if we want the scheduler to preempt?
 
                
> Add Preemption to MR2 Fair Scheduler
> ------------------------------------
>
>                 Key: MAPREDUCE-3602
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3602
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: scheduler
>            Reporter: Patrick Wendell
>            Assignee: Patrick Wendell
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira