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 "Jian He (JIRA)" <ji...@apache.org> on 2016/05/17 20:23:14 UTC
[jira] [Commented] (YARN-2877) Extend YARN to support distributed
scheduling
[ https://issues.apache.org/jira/browse/YARN-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287489#comment-15287489 ]
Jian He commented on YARN-2877:
-------------------------------
[~asuresh], [~kkaranasos], how possible is this going to branch-2 too ? At least, I see YARN-5073(refactoring) can be committed in branch-2.
Asking this because this will cause code divergence from trunk and branch-2. And other patches may require to write two versions.
One other thing is the newly added protocol buffer field, I remember that protocol buffer requires field tagged number to be the same for compatibility. Since A new field ContainerQueuingLimitProto is added in NodeHeartBeatResponse and occupied number 14, but that is only committed in trunk. If we need to add a new field in NodeHeartBeatResponse in branch-2 (YARN-4832) which also uses field number 14. This will cause branch-2 and trunk incompatible in NM heartbeat.
> 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
> Assignee: Konstantinos Karanasos
> Attachments: distributed-scheduling-design-doc_v1.pdf
>
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org