[
https://issues.apache.org/jira/browse/HADOOP-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581663#comment-13581663
]
Chris Nauroth commented on HADOOP-9318:
---------------------------------------
+1 for the patch.
Thanks for providing the additional diagnostics. I applied the patch to trunk,
built a distro, and tried various ways of stopping namenode. I did this on
Mac, Ubuntu with OpenJDK, and Windows. Everything worked fine.
I was hoping to test on a JVM that didn't have those sun.misc classes, but the
classes are present on all of my environments. I fully expect the catch clause
would handle it fine though by catching {{ExceptionInInitializerError}}.
> when exiting on a signal, print the signal name first
> -----------------------------------------------------
>
> Key: HADOOP-9318
> URL: https://issues.apache.org/jira/browse/HADOOP-9318
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.0.4-beta
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Priority: Minor
> Attachments: HADOOP-9318.001.patch
>
>
> On UNIX, it would be nice to know when a Hadoop daemon had exited on a
> signal. For example, if a daemon exited because the system administrator
> sent SIGTERM (i.e. {{killall java}}), it would be nice to know that.
> Although some of this can be deduced from context and {{SHUTDOWN_MSG}}, it
> would be nice to have it be explicit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
