hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6413) Decouple Yarn Registry API from ZK
Date Wed, 09 Aug 2017 21:06:00 GMT

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

Jian He commented on YARN-6413:
-------------------------------

Looks like the ApplicationServiceRecordKey etc. is still using the appId,  as said before,
that will be in conflict with what exists today ? 

> 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, 0003-Registry-API-api-only.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