[
https://issues.apache.org/jira/browse/HBASE-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129225#comment-13129225
]
Alex Newman commented on HBASE-2739:
------------------------------------
- Is the appropriate way to fail, just to throw? What's the science here?
- I just created a conf variable which controls whether or not this should
cause a shutdown. Are there any other cases where we do/don't want to shutdown?
Do we need a different variable for distributed / single node spliting?
> 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
> Assignee: Alex Newman
> 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.
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
