[
https://issues.apache.org/jira/browse/YARN-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193990#comment-16193990
]
Jian He commented on YARN-7198:
-------------------------------
bq. I'm looking in a directory called 'yarn-service' at documentation. If this
is the 'yarn-service', then what is the rest of YARN? service is really not a
good word to use. In fact, service is so over used in the YARN documentation
(here and elsewhere) as a whole that it's lost all meaning.
Agree it's a bit overloaded, but unfortunately didn't come up with a better
name..
bq. It's interesting that it failed to start because it couldn't connect to ZK
on localhost/127.0.0.1:2181. So I'm guessing there is a chunk of documentation
missing?
yeah.. the "hadoop.registry.dns.bind-address" is missing, it was part of the
yarn-registry effort and so documented in the yarn registry service. I'll also
add it here.
bq. hadoop.registry.dns.zone-subnet
it's not CIDR notation, sample config is like below. But I think a CIDR
notation is even simpler. I've updated the sample configs in
ServiceDiscovery.md with the changes.
{code}
<property>
<name>hadoop.registry.dns.zone-mask</name>
<value>255.255.255.0</value>
</property>
<property>
<name>hadoop.registry.dns.zone-subnet</name>
<value>172.21.195.0</value>
</property>
{code}
> Add jsvc support for RegistryDNS
> --------------------------------
>
> Key: YARN-7198
> URL: https://issues.apache.org/jira/browse/YARN-7198
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn-native-services
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Priority: Critical
> Attachments: YARN-7198-yarn-native-services.01.patch,
> YARN-7198-yarn-native-services.02.patch,
> YARN-7198-yarn-native-services.03.patch,
> YARN-7198-yarn-native-services.04.patch
>
>
> RegistryDNS should have jsvc support and be managed through the shell
> scripts, rather than being started manually. See original comments on
> YARN-7191.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]