[ 
https://issues.apache.org/jira/browse/YARN-7972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381391#comment-16381391
 ] 

Weiwei Yang commented on YARN-7972:
-----------------------------------

Hi [~leftnoteasy], [~asuresh]

Thanks for the feedback. I think I agree with [~leftnoteasy], we can remove 
{{ns:}} prefix
# app-label/<application-label>/<tag>
# app-id/<application-id>/<tag>
# self/<tag>
# not-self/<tag>
# all/<tag>
# <tag> ---> this equals to ns:self/<tag>

Note, app-label, app-id, self, not-self and all are *system-preserved namespace 
prefixes*, if any other prefix given, we will give an invalid namespace error 
during the validation. So either user uses a pre-defined namespace prefix (#1 
to #5), or do not add a namespace which actually means self. I will update the 
patch to do so.

[~asuresh],  the reason not-self and all is not yet implemented is just because 
we need more changes in AllocationTagsManager, so I would like to do this 
step-by-step. And actually there is an exception thrown in 
{{AllocationTagNamespace#parse}} when it met any forms it current doesn't 
support, so I guess that addresses your concern?

Does this sound good to you?

> 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, YARN-7972.002.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

Reply via email to