[
https://issues.apache.org/jira/browse/YARN-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300156#comment-16300156
]
Arun Suresh commented on YARN-6596:
-----------------------------------
bq. Does this work on AM failure too? ...
It is very rare for both the RM and AM to go down together, so if only the AM
restarts, the mapping will be there in the RM memory - unless BOTH the AM and
RM goes down together, in which case the re-register will solve things (AM
Re-register is required even when AM restarts and a new app appattempt is
created)
Not sure if we need anything specific in the {{ApplicationSubmissionContext}}.
It depends on how we write the client that can start the AM. It is possible for
the client to create a file with the placementconstraints and add that to the
AM's localized bits. This will ensure that the AM will have access to that file
wherever it restarts. It will then parse the constraints on startup and send it
with the register call.
> 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]
