[
https://issues.apache.org/jira/browse/YARN-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798363#comment-13798363
]
Bikas Saha commented on YARN-1222:
----------------------------------
I havent seen the patch. I would expect that logical state store operations
like storeApplication, storeToken, removeToken etc dont have to worry about
these details. They just create a list of ZK ops which then get funneled
through a common executor. This executor adds the fencing op, combines all ops
into a single zk-multi-operation and executes it. Is that how it works?
Also, we would need a takeOwnership feature that would be called before
loadState() and would perform ACL change operation to take ownership and also
setup the fencing node for subsequent operations.
> Make improvements in ZKRMStateStore for fencing
> -----------------------------------------------
>
> Key: YARN-1222
> URL: https://issues.apache.org/jira/browse/YARN-1222
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Karthik Kambatla
> Attachments: yarn-1222-1.patch, yarn-1222-2.patch
>
>
> Using multi-operations for every ZK interaction.
> In every operation, automatically creating/deleting a lock znode that is the
> child of the root znode. This is to achieve fencing by modifying the
> create/delete permissions on the root znode.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
