[
https://issues.apache.org/jira/browse/YARN-8392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564275#comment-16564275
]
Gour Saha commented on YARN-8392:
---------------------------------
Thanks [~billie.rinaldi]. Patch 4 looks good. The documentation in swagger
definition (YARN-Simplified-V1-API-Layer-For-Services.yaml), examples
(YARN-Services-Examples.md) and site documentation are quite generic since it
talks about the broader placement policy support. However, do you want to
review them once and see if we should add some specific examples for this
symmetric usecase.
> 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, YARN-8392.2.patch, YARN-8392.3.patch,
> YARN-8392.4.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
