[
https://issues.apache.org/jira/browse/YARN-7972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379640#comment-16379640
]
Weiwei Yang commented on YARN-7972:
-----------------------------------
Hi [~leftnoteasy]
#1 makes sense and I will do that in next patch.
#2 Valid concern, how about we make following specification for target key:
* ns:app-label/<application-label>/<tag>
* ns:app-id/<application-id>/<tag>
* ns:self/<tag>
* ns:not-self/<tag>
* ns:all/<tag>
* <tag> ---> this equals to ns:self/<tag>
*ns* represents for namespace. please let me know your thought.
Thanks
> Support inter-app placement constraints for allocation tags by application ID
> -----------------------------------------------------------------------------
>
> Key: YARN-7972
> URL: https://issues.apache.org/jira/browse/YARN-7972
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Priority: Major
> Attachments: YARN-7972.001.patch
>
>
> Per discussion in [this
> comment|https://issues.apache.org/jira/browse/YARN-6599focusedCommentId=16319662&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16319662]
> in YARN-6599, we need to support inter-app PC for allocation tags.
> This will help to do better placement when dealing with potential competing
> resource applications, e.g don't place two tensorflow workers from two
> different applications on one same node.
--
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
