[
https://issues.apache.org/jira/browse/YARN-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300168#comment-16300168
]
Sunil G commented on YARN-6596:
-------------------------------
bq.Not sure if we need anything specific in the ApplicationSubmissionContext.
It depends on how we write the client that can start the AM.
I think adding to ASC may not be better. Because more and more such reqs will
be coming going forward and ASC changes may not be ported back to all apps
running today.
I think it is upto AM to decide how to save that information locally(like
Arun's suggestion of file here) and work based on that as a plugin module in
case AM is failed.
> 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]
