[
https://issues.apache.org/jira/browse/YARN-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299714#comment-16299714
]
Weiwei Yang edited comment on YARN-6596 at 12/21/17 1:45 PM:
-------------------------------------------------------------
Hi [~kkaranasos]
Thanks. I have 2 follower questions
# Current implementation is a in-memory store, how these info can be recovered
on RM failure? Maybe store this info into RM state store?
# 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.
Both #1 and #2 don't have to be added in this patch, if you think they are
necessary, I will be happy to help.
Thanks.
was (Author: cheersyang):
Hi [~kkaranasos], thanks, since current implementation is a in-memory store,
how these info can be recovered on RM failure? Maybe store this info into RM
state store?
> 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]
