[
https://issues.apache.org/jira/browse/HBASE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025019#comment-13025019
]
Prakash Khemani commented on HBASE-3675:
----------------------------------------
can there be a readonly safemode until admin intervenes?
we should be liberal about ignoring errors in the last logfile in the last
block. A checksum error at the end of the last log file could be ignored (as
mentioned in HBASE-3674)
> hbase.hlog.split.skip.errors is false by default but we don't act properly
> when its true; can make for inconsistent view
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-3675
> URL: https://issues.apache.org/jira/browse/HBASE-3675
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Critical
>
> So, by default hbase.hlog.split.skip.error is false so we should not be
> skipping errors (What should we do, abort?).
> Anyways, see https://issues.apache.org/jira/browse/HBASE-3674. It has
> checksum error on near to last log BUT it writes out recovered.edits gotten
> so far. We then go and assign the regions anyways, applying edits gotten so
> far, though there are edits behind the checksum error still to be recovered.
> Not good.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
