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

Posted to issues@hbase.apache.org by "Alex Newman (JIRA)" <ji...@apache.org> on 2011/09/14 02:44:09 UTC

[jira] [Commented] (HBASE-2739) Master should fail to start if it cannot successfully split logs

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

Alex Newman commented on HBASE-2739:
------------------------------------

This looks out of date. We no longer catch/ignore exceptions in this function. Should I be looking somewhere else?

> Master should fail to start if it cannot successfully split logs
> ----------------------------------------------------------------
>
>                 Key: HBASE-2739
>                 URL: https://issues.apache.org/jira/browse/HBASE-2739
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.20.4, 0.90.0
>            Reporter: Todd Lipcon
>            Priority: Critical
>
> In trunk, in splitLogAfterStartup(), we log the error splitting, but don't shut down. Depending on configuration, we should probably shut down here rather than continue with dataloss.
> In 0.20, we print the stacktrace to stdout in verifyClusterState, but continue through and often fail to start up 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira