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

Konstantinos Karanasos commented on YARN-8113:
----------------------------------------------

Thanks for working on this, [~cheersyang].

A couple of comments:
 * I think you removed from the scheduler handler description the sentence "It 
currently supports anti-affinity constraints (no affinity or cardinality)". I 
thought we still do not have support inside the scheduler for that (only the 
processor can do this). If this is the case, we should keep this sentence.
 * Can we instead of "server" and "processor" in your AND example, use 
something like storm, zk, spark? It took me a moment to understand that 
processor and server are just tags.
 * In the {{PlacementSpec}} description, we should add the syntax for AND and 
OR.
 * Minor: You can put the "Allocation tags namespace" paragraph above the 
"Differences between node labels, attributes, and tags" para.

> Update placement constraints doc with application namespace and inter-app 
> constraints
> -------------------------------------------------------------------------------------
>
>                 Key: YARN-8113
>                 URL: https://issues.apache.org/jira/browse/YARN-8113
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: documentation
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>            Priority: Major
>         Attachments: AllocationTag_Namespace.png, DS_update.png, 
> YARN-8113.001.patch
>
>
> Once YARN-8013 is done, we will support all type of application namespace 
> types for inter-app constraints, accordingly we need to update the doc. Also 
> make sure API doc will be updated.



--
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