[
https://issues.apache.org/jira/browse/YARN-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285856#comment-15285856
]
Arun Suresh commented on YARN-4412:
-----------------------------------
[~aw], Agree with you mostly.. but as I mentioned before : I had provided a
justification.
In any case, I have re-opened YARN-5075 and posted the addendum patch there.
Given that this patch is a bit deep in the commit log and it has dependencies,
Reverting it might not be straight forward.
Wondering if it would be fine if I closed this JIRA and track the fix there ?
> Create ClusterMonitor to compute ordered list of preferred NMs for
> OPPORTUNITIC containers
> ------------------------------------------------------------------------------------------
>
> Key: YARN-4412
> URL: https://issues.apache.org/jira/browse/YARN-4412
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Fix For: 3.0.0-alpha1
>
> Attachments: YARN-4412-yarn-2877.v1.patch,
> YARN-4412-yarn-2877.v2.patch, YARN-4412-yarn-2877.v3.patch,
> YARN-4412-yarn-2877.v4.patch, YARN-4412-yarn-2877.v5.patch,
> YARN-4412-yarn-2877.v6.patch, YARN-4412.007.patch, YARN-4412.008.patch,
> YARN-4412.009.patch, YARN-4412.addendum-001.patch, YARN-4412.find-bugs.patch
>
>
> Introduce a Cluster Monitor that aggregates load information from individual
> Node Managers and computes an ordered list of preferred Node managers to be
> used as target Nodes for OPPORTUNISTIC container allocations.
> This list can be pushed out to the Node Manager (specifically the AMRMProxy
> running on the Node) via the Allocate Response. This will be used to make
> local Scheduling decisions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
