You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Ellen Hui (JIRA)" <ji...@apache.org> on 2017/05/12 17:22:04 UTC
[jira] [Updated] (YARN-6413) Decouple Yarn Registry API from ZK
[ https://issues.apache.org/jira/browse/YARN-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ellen Hui updated YARN-6413:
----------------------------
Attachment: 0001-WIP-Registry-API-v2.patch
WIP. [~jianhe], could you please take a look at the API and let me know if it looks reasonable to you? If so, I will clean it up and finish the implementation and tests.
> Decouple Yarn Registry API from ZK
> ----------------------------------
>
> Key: YARN-6413
> URL: https://issues.apache.org/jira/browse/YARN-6413
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: amrmproxy, api, resourcemanager
> Reporter: Ellen Hui
> Assignee: Ellen Hui
> Attachments: 0001-WIP-Registry-API-v2.patch
>
>
> Right now the Yarn Registry API (defined in the RegistryOperations interface) is a very thin layer over Zookeeper. This jira proposes changing the interface to abstract away the implementation details so that we can write a FS-based implementation of the registry service, which will be used to support AMRMProxy HA.
> The new interface will use register/delete/resolve APIs instead of Zookeeper-specific operations like mknode.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org