[jira] [Updated] (YARN-6413) Decouple Yarn Registry API from ZK

["Ellen Hui (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ellen Hui updated YARN-6413:
----------------------------
    Attachment: 0002-Registry-API-v2.patch

Addressed comments from [~jianhe]:

* The V2 has every method used by RegistryDNS except for monitorRegistryEntries and registrPathListener, which were added in a yarn-native-services commit.
* Removed extra imports from RegistryOperations
* The path was rearranged in order to flatten the namespace
* removed getSubpathsForUserServiceRecordKey
* Removed catch stub and replaced with a proper log

> 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-Registry-API-v2.patch, 0002-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.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org