[
https://issues.apache.org/jira/browse/YARN-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300050#comment-16300050
]
Arun Suresh commented on YARN-6596:
-----------------------------------
[~cheersyang], to answer both your queries:
bq. YARN-6595 adds placement constraints context in application level, should
we extract the info during app registration and add them into the placement
constraints manager? Also make sure it is removed when its lifecycle finished.
Yup. We are doing this in YARN-7612 patch. Please take a look a the latest
patch there. The {{PlacementProcessor::registerApplicationMaster()}} does this.
But good point, we would have to remove the same when the app completes (will
handle that in the finish).
bq. Current implementation is a in-memory store, how these info can be
recovered on RM failure? Maybe store this info into RM state store?
Currently, the PlacementConstraints are added via the
registerApplicationMaster() call (YARN-6595). As per the RM failover protocol,
one the AM has detected that the RM has failed over, am AM would have to
re-register - which means it has to call registerApplicationMaster again -
which means the AM has to resend the PlacementConstraints. This means we wont
have to persist the PlacementConstraint mappings in the state store. It will be
automatically recovered.
> 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]
