[
https://issues.apache.org/jira/browse/HADOOP-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724470#comment-14724470
]
Sangjin Lee commented on HADOOP-12364:
--------------------------------------
There are service management mechanisms (e.g. monit restart) that are somewhat
haphazard in terms of the stop and start timing. We came across that issue.
I wouldn't quite call this bug a blocker (probably a minor bug), but it's
definitely useful defensive fix. +1 for it.
> Deleting pid file after stop is causing the daemons to keep restarting
> -----------------------------------------------------------------------
>
> Key: HADOOP-12364
> URL: https://issues.apache.org/jira/browse/HADOOP-12364
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Siqi Li
> Priority: Blocker
> Attachments: HADOOP-12364.v1.patch
>
>
> pid files are deleting in 5 seconds after we stop the daemons. If a start
> command were executed within the 5 seconds, the pid file will be overwrite
> with a new pid. However, this pid file is going to be deleted by the former
> stop command. This is causing the monitoring service to lose track of the
> daemons, hence keep rebooting them
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
