hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ellen Hui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6413) Decouple Yarn Registry API from ZK
Date Mon, 24 Jul 2017 17:59:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16098902#comment-16098902
] 

Ellen Hui commented on YARN-6413:
---------------------------------

bq. 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.

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.

bq. 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.

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.

> 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


Mime
View raw message