You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2019/12/20 22:17:00 UTC

[jira] [Resolved] (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

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

Michael Stack resolved HBASE-3675.
----------------------------------
    Resolution: Won't Fix

Stale. Context is different now.

> 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: Michael 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 was sent by Atlassian Jira
(v8.3.4#803005)