[
https://issues.apache.org/jira/browse/YARN-8392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520660#comment-16520660
]
Billie Rinaldi commented on YARN-8392:
--------------------------------------
This patch removes the validation code in ServiceApiUtil that restricts the
placement constraint tags and adds a test for multi component anti affinity. I
created a new test class for this test, and I also moved the existing placement
policy test from TestYarnNativeServices to the new class, TestPlacementPolicy.
> Allow multiple tags for anti-affinity placement policy in service
> specification
> -------------------------------------------------------------------------------
>
> Key: YARN-8392
> URL: https://issues.apache.org/jira/browse/YARN-8392
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Priority: Critical
> Attachments: YARN-8392.1.patch
>
>
> Currently the service client code is restricting a component's target tags to
> include only a single tag, the component name. I have a use case for two
> components having anti-affinity with themselves and with each other. The YARN
> placement policies support this, but the service framework isn't allowing it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
