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

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

I tried out patch 4. There seems to be an assembly issue. The hadoop-registry 
jar is included in the dist tarball at 
hadoop-dist/target/hadoop-3.3.0-SNAPSHOT/share/hadoop/tools/lib/hadoop-registry-3.3.0-SNAPSHOT.jar
 instead of an expected location such as share/hadoop/common/. I manually 
copied the jar to share/hadoop/common/ in my tarball install and was able to 
start RegistryDNS both with the yarn command and the hadoop command. I verified 
that I could perform DNS lookups for container hostnames in both cases.

So far I've only tried the daemon in privileged mode. I'm having an issue 
stopping the daemon, but this appears to be an existing issue not caused by the 
patch. I'll have to dig a bit deeper to determine whether it's a problem in my 
installation or it's a bug.

> 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, HADOOP-15821.003.patch, HADOOP-15821.004.patch, 
> HADOOP-15821.005.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