You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2012/08/06 20:49:02 UTC
[jira] [Commented] (HADOOP-8656) backport forced daemon shutdown of
HADOOP-8353 into branch-1
[ https://issues.apache.org/jira/browse/HADOOP-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429338#comment-13429338 ]
Steve Loughran commented on HADOOP-8656:
----------------------------------------
If you suspend a hadoop daemon with a {{kill -STOP $pid}}, the {{service hadoop-namenode stop}} operation will not actually terminate the process -it issues a kill -TERM "hint".
HADOOP-8353 forces the shutdown with a sleep followed by a kill -9 if there is a process with that pid still listed. This forces the shutdown, and should have no adverse side effects provided that Pid doesn't get reused during the sleep phase.
This JIRA covers backporting it to 1.1 and trunk
> backport forced daemon shutdown of HADOOP-8353 into branch-1
> ------------------------------------------------------------
>
> Key: HADOOP-8656
> URL: https://issues.apache.org/jira/browse/HADOOP-8656
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 1.0.3
> Environment: init.d
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 1.1.0
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> the init.d service shutdown code doesn't work if the daemon is hung -backporting the portion of HADOOP-8353 that edits bin/hadoop-daemon.sh corrects this
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira