Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 22 Jun 2017 04:03:02 +0000 (UTC)
From: "Jian He (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13060222.1490838064000.76813.1498104182491@Atlassian.JIRA>
In-Reply-To: <JIRA.13060222.1490838064000@Atlassian.JIRA>
References: <JIRA.13060222.1490838064000@Atlassian.JIRA> <JIRA.13060222.1490838064824@jira-lw-us.apache.org>
Subject: [jira] [Commented] (YARN-6413) Decouple Yarn Registry API from ZK
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 22 Jun 2017 04:03:09 -0000


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

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

Hi Ellem, sorry, I was looking at the wrong patch. some comments on the latest patch:

- The patch removed some methods which are actually used by RegistryDNS, can you check the RegistryDNSServer class and see if we need to add them back or make it use the alternative methods ? 
- RegistryOpertions: InvalidRecordException and NoRecordException can be removed from the method signature
- getPathForServiceRecordKey: the patch changed the path naming , any reason for not keeping the original naming?
- remove the getSubpathsForUserServiceRecordKey method, it's unused
- should use LOG.error instead
{code}
    } catch (InvalidRegistryKeyException e) {
      // TODO Auto-generated catch block
      e.printStackTrace();
    }
{code}

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