[
https://issues.apache.org/jira/browse/YARN-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798067#comment-13798067
]
Tsuyoshi OZAWA commented on YARN-1307:
--------------------------------------
Thanks for your review, Vinod and Jian!
> RMDelegationToken is not application specific, user can also explicitly say
> getDelegationToken, should not be stored along with app info.
I overlooked this. Then, the following znode structure is correct one.
{code}
ROOT_DIR_PATH
|--- RM_APP_ROOT
| |----- (#ApplicationId1)
| | |----- ATTEMPT_IDS
| | |----- (#ApplicationAttemptIds)
| |
| |----- (#ApplicationId2)
| |----- ATTEMPT_IDS
| |----- (#ApplicationAttemptIds)
| ,,,,
|--- RM_DT_SECRET_MANAGER_ROOT
|----- RMDTSequenceNumber_(SequenceNumber)
|----- RMDelegationToken_(#SequenceNumber)
{code}
As you mentioned, ZK does NOT support 'directory' removal. We can implement it
with ZK's getChildren and multi delete APIs.
> Rethink znode structure for RM HA
> ---------------------------------
>
> Key: YARN-1307
> URL: https://issues.apache.org/jira/browse/YARN-1307
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Tsuyoshi OZAWA
> Assignee: Tsuyoshi OZAWA
>
> Rethink for znode structure for RM HA is proposed in some JIRAs(YARN-659,
> YARN-1222). The motivation of this JIRA is quoted from Bikas' comment in
> YARN-1222:
> {quote}
> We should move to creating a node hierarchy for apps such that all znodes for
> an app are stored under an app znode instead of the app root znode. This will
> help in removeApplication and also in scaling better on ZK. The earlier code
> was written this way to ensure create/delete happens under a root znode for
> fencing. But given that we have moved to multi-operations globally, this isnt
> required anymore.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
