[
https://issues.apache.org/jira/browse/YARN-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099345#comment-16099345
]
Jian He commented on YARN-6413:
-------------------------------
bq. I did not remove any methods, I just didn't add the ones that exist in
yarn-native-services but not trunk. I thought doing so would probably cause
more conflicts than not.
looks like RegistryUtils#extractServiceRecords is removed. Do you mind change
RegistryDNSServer to use the new methods ? (i.e. make this patch compile with
yarn-native-services branch)
bq. My understanding was that DNS went through ZK directly without going
through the interface, so it wouldn't be affected by the service records
setting up the path differently. I can change the path construction back for
the ZK impl if it needs that.
The DNS today depends on the ZK path layout to reconstruct the service record.
So changing the zk path will break DNS.
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
