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

Konstantinos Karanasos commented on YARN-6599:
----------------------------------------------

[~wangda] and [~asuresh]:
* I think we should not introduce node partitions in this JIRA. Not only for 
the size of the patch, but because semantically it belongs to a different JIRA.
In general, this is a complicated feature we are adding. Let's get a first 
version with node and rack, and once we are convinced this is working, we can 
add the node partitions, after we agree on how we do this properly and in a 
clean way.
* What we did in YARN-7613 is to restrict the scope of a constraint to the 
application that is defining it for the first version, so that we do not have 
to deal with prefixes. Again, we will eventually need something like this, but 
I don't think it should be introduced in this JIRA.
* I can be convinced to remove the SELF target, but let's discuss before taking 
action on this. I need to think a bit more about it -- it might not be just 
syntactic sugar given have decided to not include the source tags in the 
constraint itself.

I think we should chat offline to converge faster on this couple of things.

> Support rich placement constraints in scheduler
> -----------------------------------------------
>
>                 Key: YARN-6599
>                 URL: https://issues.apache.org/jira/browse/YARN-6599
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: YARN-6599-YARN-6592.003.patch, 
> YARN-6599-YARN-6592.004.patch, YARN-6599-YARN-6592.005.patch, 
> YARN-6599-YARN-6592.006.patch, YARN-6599-YARN-6592.007.patch, 
> YARN-6599-YARN-6592.008.patch, YARN-6599-YARN-6592.wip.002.patch, 
> YARN-6599.poc.001.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to