Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Later
-
0.20.4, 0.90.0
-
None
-
None
Description
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
Attachments
Issue Links
- relates to
-
HBASE-3675 hbase.hlog.split.skip.errors is false by default but we don't act properly when its true; can make for inconsistent view
- Closed