[
https://issues.apache.org/jira/browse/YARN-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099352#comment-16099352
]
Ellen Hui edited comment on YARN-6413 at 7/25/17 1:10 AM:
----------------------------------------------------------
bq. 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)
Ah, I see. RegistryUtils#extractServiceRecords is one of the methods that
depends on having the hierarchical namespace, which is why it was removed. I
can add a select-multiple method with a filter of some sort, would that work?
The point of this from our end was to abstract away the path.
Right now yarn-native-services doesn't compile for me with a pom.xml error
(pulled just now), is the branch healthy?
bq. The DNS today depends on the ZK path layout to reconstruct the service
record. So changing the zk path will break DNS.
Ok, I will put the ZK path layout back to the way it was before.
was (Author: ellenfkh):
bq: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)
Ah, I see. RegistryUtils#extractServiceRecords is one of the methods that
depends on having the hierarchical namespace, which is why it was removed. I
can add a select-multiple method with a filter of some sort, would that work?
The point of this from our end was to abstract away the path.
Right now yarn-native-services doesn't compile for me with a pom.xml error
(pulled just now), is the branch healthy?
bq:The DNS today depends on the ZK path layout to reconstruct the service
record. So changing the zk path will break DNS.
Ok, I will put the ZK path layout back to the way it was before.
> 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
