You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/21 23:50:39 UTC

[jira] [Resolved] (HDFS-351) Could FSEditLog report problems more elegantly than with System.exit(-1)

     [ https://issues.apache.org/jira/browse/HDFS-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved HDFS-351.
-----------------------------------

    Resolution: Incomplete

edits logging got majorly reworked. closing as stale.

> Could FSEditLog report problems more elegantly than with System.exit(-1)
> ------------------------------------------------------------------------
>
>                 Key: HDFS-351
>                 URL: https://issues.apache.org/jira/browse/HDFS-351
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Steve Loughran
>            Priority: Minor
>
> When FSEdit encounters problems, it prints something and then exits.
> It would be better for any in-JVM deployments of FSEdit for these to be raised in some other way (such as throwing an exception), rather than taking down the whole JVM. That could be in JUnit tests, or it could be inside other applications. Test runners and the like can intercept those System.exit() calls with their own Security Manager -often turning the System.exit() operation into an exception there and then. If FSEdit did that itself, it may be easier to stay in control. 
> The current approach has some benefits -it can exit regardless of which thread has encountered problems, but it is tricky to test.



--
This message was sent by Atlassian JIRA
(v6.2#6252)