[
https://issues.apache.org/jira/browse/YARN-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billie Rinaldi updated YARN-7198:
---------------------------------
Attachment: YARN-7198-yarn-native-services.01.patch
Attaching patch 01. I also noticed that the registry module needed some
dependency analysis, so I cleaned up the pom in this patch. I tried out the
privileged launch, and it mostly worked. However, while I end up with two pid
files with the correct pids (one for the privileged process and one for the
yarn process), both processes have the same pidfile flag, -pidfile
/tmp/hadoop-yarn-root-registrydns.pid. When I use yarn --daemon stop
registrydns, it prints an error (while successfully stopping the daemon):
{noformat}
$ ls /tmp/*registrydns.pid
hadoop-yarn-root-registrydns.pid privileged-root-registrydns.pid
$ cat /tmp/privileged-root-registrydns.pid
12200
$ cat /tmp/hadoop-yarn-root-registrydns.pid
12208
$ yarn --daemon stop registrydns
cat: /tmp/hadoop-yarn-root-registrydns.pid: No such file or directory
WARNING: pid has changed for registrydns, skip deleting pid file
cat: /tmp/hadoop-yarn-root-registrydns.pid: No such file or directory
WARNING: daemon pid has changed for registrydns, skip deleting daemon pid file
{noformat}
I will keep looking into it; maybe I am missing some setting.
> 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
>
>
> 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]
