[
https://issues.apache.org/jira/browse/YARN-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662173#comment-13662173
]
Vinod Kumar Vavilapalli commented on YARN-624:
----------------------------------------------
bq. I would love to have it right now for storm too. If you want me to sign up
as a use case I am happy to.
This is exactly the kind of concrete use-case I was asking for, not some made
up use-case which *may* make sense. Yes please, it will be great if you sign up
and lay down important things that you need.
Like I said, I am not against adding this, we need to make sure we are
addressing the right requirements. Otherwise, we'll get lost in the myriad
scheduler features that we *can* implement, but of little use.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
