[
https://issues.apache.org/jira/browse/YARN-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289535#comment-15289535
]
Wangda Tan commented on YARN-2877:
----------------------------------
An additional note:
Junping and I investigated PB compatible cases when adding new fields to middle
of a proto.
Let's say:
PB1Proto:
{code}
optional int32 w = 1;
optional int32 x = 2;
optional int32 z = 4;
{code}
PB2Proto:
{code}
optional int32 w = 1;
optional int32 x = 2;
optional int32 y = 3;
optional int32 z = 4;
{code}
PB2Proto can read PB1Proto without any issue.
So next time we should not update sequence of fields in trunk/branch-2, what we
need to do is to make sure fields of protos across branches has same id.
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
