[
https://issues.apache.org/jira/browse/HADOOP-15066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263168#comment-16263168
]
Arpit Agarwal commented on HADOOP-15066:
----------------------------------------
The error is from {{hadoop_stop_daemon}} in _hadoop-functions.sh_.
{code}
pid=$(cat "$pidfile")
kill "${pid}" >/dev/null 2>&1
...
cur_pid=$(cat "$pidfile")
...
if [[ "${pid}" = "${cur_pid}" ]]; then
rm -f "${pidfile}" >/dev/null 2>&1
else
hadoop_error "WARNING: pid has changed for ${cmd}, skip deleting pid
file"
{code}
It looks like jsvc auto-deletes the pid file when the process is killed with
SIGTERM. The check for changed pid likely needs to be skipped if the pid file
doesn't exist.
> Spurious error stopping secure datanode
> ---------------------------------------
>
> Key: HADOOP-15066
> URL: https://issues.apache.org/jira/browse/HADOOP-15066
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Affects Versions: 3.0.0
> Reporter: Arpit Agarwal
>
> Looks like there is a spurious error when stopping a secure datanode.
> {code}
> # hdfs --daemon stop datanode
> cat: /var/run/hadoop/hdfs//hadoop-hdfs-root-datanode.pid: No such file or
> directory
> WARNING: pid has changed for datanode, skip deleting pid file
> cat: /var/run/hadoop/hdfs//hadoop-hdfs-root-datanode.pid: No such file or
> directory
> WARNING: daemon pid has changed for datanode, skip deleting daemon pid file
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
