[
https://issues.apache.org/jira/browse/YARN-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300178#comment-16300178
]
Weiwei Yang commented on YARN-6596:
-----------------------------------
bq. if only the AM restarts, the mapping will be there in the RM memory
Yes, that should be most of the cases. Since the mapping key was the
applicationId, this should be fine, thanks.
bq. It is possible for the client to create a file with the placement
constraints
Not sure if this has been discussed, I would expect a file or a configurable
property, which might be the most consumable approach by clients. But this will
need a *parser*.
> Introduce Placement Constraint Manager module
> ---------------------------------------------
>
> Key: YARN-6596
> URL: https://issues.apache.org/jira/browse/YARN-6596
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Konstantinos Karanasos
> Assignee: Konstantinos Karanasos
> Attachments: YARN-6596-YARN-6592.001.patch
>
>
> This RM module will be responsible for storing placement constraints,
> allocation tags, and node attributes.
> It will be used when determining the placement of SchedulingRequests with
> constraints.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
