[
https://issues.apache.org/jira/browse/YARN-6593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110175#comment-16110175
]
Konstantinos Karanasos commented on YARN-6593:
----------------------------------------------
Regarding the class with examples, as you say, let's move examples to a
separate JIRA. Especially given that placement constraints can be specified
both at the container level (YARN-6594) and the application level (YARN-6595).
It would be good to give all the possible ways to define constraints there.
I would like to understand better the use cases that would require allocation
tags to have values. But let's move the discussion to YARN-6594.
BTW, to be precise, allocation tags in constraints are modeled as a set of
values (not a single value) with key being null. We opted for this approach
after discussions with [~leftnoteasy] and [[email protected]] in order to
not need multiple constraint objects if we want to specify a list of tags in
the constraint.
PS: I am traveling today, thus the late responses.
> [API] Introduce Placement Constraint object
> -------------------------------------------
>
> Key: YARN-6593
> URL: https://issues.apache.org/jira/browse/YARN-6593
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Konstantinos Karanasos
> Assignee: Konstantinos Karanasos
> Attachments: YARN-6593.001.patch, YARN-6593.002.patch,
> YARN-6593.003.patch, YARN-6593.004.patch, YARN-6593.005.patch,
> YARN-6593.006.patch, YARN-6593.007.patch, YARN-6593.008.patch
>
>
> Just removed Fixed version and moved it to target version as we set fix
> version only after patch is committed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
