hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj K (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2877) Extend YARN to support distributed scheduling
Date Mon, 24 Nov 2014 09:34:15 GMT

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

Devaraj K commented on YARN-2877:
---------------------------------

+1 for the idea [~sriramsrao], [~curino] . I just wanted to know these if I am not missing
something from the above.

1. If the OPTIMISTIC Container is assigned to AM, and also at the same time RM assigned a
container i.e. CONSERVATIVE for the same resource, which one NM will consider and start it?

2. If the OPTIMISTIC Container is assigned to AM and started it, and NM receives a container
start request for CONSERVATIVE and resources are not available, will the NM preempt the running
OPTIMISTIC Containers or it will make CONSERVATIVE request to wait for completing the OPTIMISTIC
Containers?

3. Any provision for AM to request OPTIMISTIC containers in the remote NM also?


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

Mime
View raw message