[jira] [Commented] (HADOOP-8096) add single point where System.exit() is called for better handling in containers

["Guillaume Nodet (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407928#comment-13407928 ] 

Guillaume Nodet commented on HADOOP-8096:
-----------------------------------------

Fwiw, I've been able to run hadoop in osgi (I'm working on patches right now) and I haven't hit any issues with System.exit being called.
I think most of the calls are in Main classes (tools or main runners) and can be avoided by controlling the configuration in advance.
For those cases, I think it would be better to have the code throw an exception and catch it in the respective main() methods and call System.exit() there.
In OSGi, the main() methods would not be called, to the OSGi layer would have a way to intercept the problems gracefully.

                
> add single point where System.exit() is called for better handling in containers
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-8096
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8096
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: util
>    Affects Versions: 0.24.0
>            Reporter: Steve Loughran
>            Assignee: Csaba Miklos
>            Priority: Trivial
>             Fix For: 0.24.0
>
>         Attachments: HADOOP-8096.patch
>
>
> with plans for OSGI integration afoot in HADOOP-7977, Hadoop needs unified place where System.exit() calls. When one runs any bit of Hadoop in a containers the container will block those exits with a security manager and convert the calls into security exceptions. A single exit method would enable such exceptions to be logged, and conceivably handled slightly more gracefully (e.g. tell the daemon to die).

--
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