[
https://issues.apache.org/jira/browse/YARN-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222876#comment-14222876
]
Konstantinos Karanasos commented on YARN-2877:
----------------------------------------------
[~devaraj], to answer your questions:
# Guaranteed-start containers always have priority over queueable ones. Thus,
in the case you describe, if not both requests can be accommodated by the NM,
the guaranteed-start will start first.
# If the queueable one was started before the guaranteed-start arrived, it will
be pre-empted/killed for the guaranteed-start to begin execution.
# Queueable requests are submitted by the AM in the Local RM running in the
same node as the AM, but those requests can be queued at any NM of the cluster
(we pick at each moment the most idle ones to queue those requests).
> Extend YARN to support distributed scheduling
> ---------------------------------------------
>
> Key: YARN-2877
> URL: https://issues.apache.org/jira/browse/YARN-2877
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: nodemanager, resourcemanager
> Reporter: Sriram Rao
>
> This is an umbrella JIRA that proposes to extend YARN to support distributed
> scheduling. Briefly, some of the motivations for distributed scheduling are
> the following:
> 1. Improve cluster utilization by opportunistically executing tasks otherwise
> idle resources on individual machines.
> 2. Reduce allocation latency. Tasks where the scheduling time dominates
> (i.e., task execution time is much less compared to the time required for
> obtaining a container from the RM).
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
