[
https://issues.apache.org/jira/browse/YARN-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093802#comment-16093802
]
Jian He commented on YARN-6413:
-------------------------------
In RegistryDNSServer, all the methods removed are essential to registryDNS -
the implementation of RegistryDNS is depending on the zookeeper’s listener
functionality. This is one big difference from the state store implementation.
we can not remove those methods.
bq. The path was rearranged in order to flatten the namespace
The path is used by RegistryDNSServer for reconstructing the DNS record(e.g.
BaseServiceRecordProcessor#getContainerName). If we change the path, everything
there will break. Also, the registry documentation needs to change.
can you make sure the patch does not break existing stuff ? it’s fine to
abstract out the interface, but breaking existing functionalities will be
another big problem.
> 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: [email protected]
For additional commands, e-mail: [email protected]
