[
https://issues.apache.org/jira/browse/YARN-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227626#comment-16227626
]
Arun Suresh commented on YARN-6940:
-----------------------------------
bq. what is the reason to set relaxLocality to true in the first place?
This is actually an artefact of the FairScheduler. It throws an exception if
the relax locality of a node local request is false (Relevant code is
[here|https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSAppAttempt.java#L966-L971]).
The CapacityScheduler does not really mind it.
> FairScheduler: Enable Container update CodePaths and container resize testcase
> ------------------------------------------------------------------------------
>
> Key: YARN-6940
> URL: https://issues.apache.org/jira/browse/YARN-6940
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Attachments: YARN-6940.001.patch
>
>
> After YARN-6216, the Container Update (which includes Resource increase and
> decrease) code-paths are mostly scheduler agnostic.
> This JIRA tracks the final minor change needed in the FairScheduler. It also
> re-enables the {{TestAMRMClient#testAMRMClientWithContainerResourceChange}}
> test for the FairScheduler - which verifies that it works for the
> FairScheduler.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
