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

Hudson commented on YARN-6413:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13171 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/13171/])
YARN-6413. FileSystem based Yarn Registry implementation. (Ellen Hui via 
(subru: rev ed24da3dd73c137b44235e525112056ace6d3843)
* (add) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-registry/src/test/java/org/apache/hadoop/registry/client/impl/TestFSRegistryOperationsService.java
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-registry/src/main/java/org/apache/hadoop/registry/client/types/ServiceRecord.java
* (add) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-registry/src/main/java/org/apache/hadoop/registry/client/impl/FSRegistryOperationsService.java


> FileSystem based Yarn Registry implementation
> ---------------------------------------------
>
>                 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
>             Fix For: 2.9.0, 3.0.0, 3.1.0
>
>         Attachments: 0001-Registry-API-v2.patch, 
> 0001-YARN-6413-Yarn-Registry-FS-Implementation.patch, 
> 0002-Registry-API-v2.patch, 0003-Registry-API-api-only.patch, 
> 0004-Registry-API-api-stubbed.patch, YARN-6413.v1.patch, YARN-6413.v2.patch, 
> YARN-6413.v3.patch, YARN-6413.v4.patch, YARN-6413.v5.patch, 
> YARN-6413.v6.patch, YARN-6413.v7.patch
>
>
> Add a RegistryOperations implementation that writes records to the file 
> system. This does not include any changes to the API, to avoid compatibility 
> issues.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to