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

Billie Rinaldi commented on HADOOP-15821:
-----------------------------------------

Hi [~elgoiri], thanks for working on this patch! It's looking good so far. 
Another area we'll have to address is the RegistryDNS daemon command in 
hadoop-yarn-project/hadoop-yarn/bin/yarn as well as the exports 
YARN_REGISTRYDNS_SECURE_USER, YARN_REGISTRYDNS_SECURE_EXTRA_OPTS in 
hadoop-yarn-project/hadoop-yarn/conf/yarn-env.sh. This might be a candidate for 
backwards compatibility. Maybe we could keep the yarn command and env vars for 
starting the daemon as deprecated, while also introducing a hadoop command? I'm 
open to suggestions.

There is also some documentation about how to configure and start RegistryDNS 
here:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/ServiceDiscovery.md
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/RegistryDNS.md

I'll try to test out the patch and see if I can find anything else.


> Move Hadoop YARN Registry to Hadoop Registry
> --------------------------------------------
>
>                 Key: HADOOP-15821
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15821
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Íñigo Goiri
>            Assignee: Íñigo Goiri
>            Priority: Major
>         Attachments: HADOOP-15821.000.patch, HADOOP-15821.001.patch, 
> HADOOP-15821.002.patch
>
>
> Currently, Hadoop YARN Registry is in YARN. However, this can be used by 
> other parts of the project (e.g., HDFS). In addition, it does not have any 
> real dependency to YARN.
> We should move it into commons and make it Hadoop Registry.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to