[
https://issues.apache.org/jira/browse/YARN-10219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076724#comment-17076724
]
Eric Yang commented on YARN-10219:
----------------------------------
I am unsure the reason that unit test failed for patch 002. It only fixed
checkstyle issue in patch 1. The exact anti affinity test pass with success in
my cluster environment, and I am unable to get it to fail locally. I suspect
it maybe dynamic detection of number of vcore to use per node manager in
Jenkins environment which is different from my laptop. My laptop is saturated
at 4 cpu cores, which may prevent additional containers to start and allowed
test case to pass. I resubmit patch 2 as patch 3 for retest. If this fails
again, I will add vcore restriction to this test case to prevent fail on more
powerful hardware.
> YARN service placement constraints is broken
> --------------------------------------------
>
> Key: YARN-10219
> URL: https://issues.apache.org/jira/browse/YARN-10219
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.1.0, 3.2.0, 3.1.1, 3.1.2, 3.3.0, 3.2.1, 3.1.3
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Attachments: YARN-10219.001.patch, YARN-10219.002.patch,
> YARN-10219.003.patch
>
>
> YARN service placement constraint does not work with node label nor node
> attributes. Example of placement constraints:
> {code}
> "placement_policy": {
> "constraints": [
> {
> "type": "AFFINITY",
> "scope": "NODE",
> "node_attributes": {
> "label":["genfile"]
> },
> "target_tags": [
> "ping"
> ]
> }
> ]
> },
> {code}
> Node attribute added:
> {code} ./bin/yarn nodeattributes -add "host-3.example.com:label=genfile"
> {code}
> Scheduling activities shows:
> {code} <diagnostic> Node does not match partition or placement constraints,
> unsatisfied PC expression="in,node,ping", target-type=ALLOCATION_TAG
> </diagnostic>
> <count>1</count>
> <nodeIds>host-3.example.com:45454</nodeIds>{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
