[
https://issues.apache.org/jira/browse/BIGTOP-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shaposhnik updated BIGTOP-1129:
-------------------------------------
Attachment: 0001-BIGTOP-1129.-Cannot-stop-datanode-through-init-scrip.patch
[~bmahe] thanks a bunch for detailed instructions! It was indeed a difference
between what we ship by default and what our Puppet deploys. I'm attaching a
trivial patch that disables all the tweaks that are now coming to use as part
of hadoop-env.sh from upstream. This makes it so that the file can still be
used as an example, but it doesn't really mess our environment up.
Please review ASAP.
> Cannot stop datanode through init script
> ----------------------------------------
>
> Key: BIGTOP-1129
> URL: https://issues.apache.org/jira/browse/BIGTOP-1129
> Project: Bigtop
> Issue Type: Bug
> Components: Init scripts
> Affects Versions: 0.7.0
> Environment: Centos
> Reporter: Bruno Mahé
> Fix For: 0.7.0
>
> Attachments:
> 0001-BIGTOP-1129.-Cannot-stop-datanode-through-init-scrip.patch
>
>
> {noformat}sudo /etc/init.d/hadoop-hdfs-datanode stop{noformat}
> When starting the datanode, I do see a correct pid file in
> /var/run/hadoop-hdfs/hadoop-hdfs-datanode.pid but whenever I call the stop
> command, the pid file disappear while the process still exists.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
