[
https://issues.apache.org/jira/browse/YARN-6593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095049#comment-16095049
]
Wangda Tan commented on YARN-6593:
----------------------------------
[~chris.douglas],
bq. Do we want to support users adding new transforms? If not, some of the
implementation details could be package-private.
I think we should not support users adding new transforms.
bq. Wangda Tan: what are the semantics of updated constraints? ...
Yeah we missed it in our design doc, however I found it is very important
otherwise we cannot support complex placement request which need to be updated.
Regarding to semantics, I prefer to apply to all containers placed
subsequently, this is also the closest behavior of existing YARN. We just need
to verify updated placement request is still valid, probably we don't need to
restricted to some parameters.
What's your thoughts here?
> [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
> Fix For: 3.0.0-alpha3
>
> Attachments: YARN-6593.001.patch, YARN-6593.002.patch,
> YARN-6593.003.patch, YARN-6593.004.patch
>
>
> This JIRA introduces an object for defining placement constraints.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
