[
https://issues.apache.org/jira/browse/YARN-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285609#comment-15285609
]
Arun Suresh commented on YARN-4412:
-----------------------------------
[~gtCarrera9], Please note that both the
[11226|https://builds.apache.org/job/PreCommit-YARN-Build/11226] and
[11235|https://builds.apache.org/job/PreCommit-YARN-Build/11235] were based off
the same patch and were kicked off roughly around the same time.. The later
(for which you see a lot of javadoc and mvninstall -1s spewed by Jenkins) is
due to some other issue with the execution environment..
In any case, with respect to
[11226|https://builds.apache.org/job/PreCommit-YARN-Build/11226]
# The checkstyle issues, most of which was caused by indentation errors have
been corrected in YARN-2888
# The unit test failures are spurious and I have raised YARN-5091 to track and
possibly fix them
# What remains are the findbugs issues:
## The *System.exit()* is what we are addressing with the re-opening of this
JIRA
## The inconsistent synchronization issues in {{NodeStatusPBImpl}}.. i believe
should be left as it is... since the class is always created and used within
the NodeStatusUpdater and never generally shared.
> 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.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]
