You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Lei Guo (JIRA)" <ji...@apache.org> on 2015/06/30 16:35:07 UTC

[jira] [Commented] (YARN-624) Support gang scheduling in the AM RM protocol

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

Lei Guo commented on YARN-624:
------------------------------

[~john.lilley@redpoint.net], with your use case, do you also have data locality preference? If yes, whether each container may have separate data locality preference?

> Support gang scheduling in the AM RM protocol
> ---------------------------------------------
>
>                 Key: YARN-624
>                 URL: https://issues.apache.org/jira/browse/YARN-624
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, scheduler
>    Affects Versions: 2.0.4-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>
> Per discussion on YARN-392 and elsewhere, gang scheduling, in which a scheduler runs a set of tasks when they can all be run at the same time, would be a useful feature for YARN schedulers to support.
> Currently, AMs can approximate this by holding on to containers until they get all the ones they need.  However, this lends itself to deadlocks when different AMs are waiting on the same containers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)