[
https://issues.apache.org/jira/browse/HBASE-13811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570198#comment-14570198
]
Duo Zhang edited comment on HBASE-13811 at 6/3/15 3:02 AM:
-----------------------------------------------------------
Write a testcase. It fails for me with
{noformat}
java.lang.AssertionError: actual array was null
at
org.apache.hadoop.hbase.regionserver.TestSplitWalDataLoss.test(TestSplitWalDataLoss.java:153)
{noformat}
I think the fix should also be applied to branch-1.1 since it will cause data
loss even if we turn off flush per CF(but no issues if you turn on DLR...).
[~ndimiduk]
was (Author: apache9):
Write a testcase. It fails for me with
{noformat}
java.lang.AssertionError: actual array was null
at
org.apache.hadoop.hbase.regionserver.TestSplitWalDataLoss.test(TestSplitWalDataLoss.java:153)
{noformat}
I think the fix should also be applied to branch-1.1 since it will cause data
loss even if we turn off flush per CF. [~ndimiduk]
> Splitting WALs, we are filtering out too many edits -> DATALOSS
> ---------------------------------------------------------------
>
> Key: HBASE-13811
> URL: https://issues.apache.org/jira/browse/HBASE-13811
> Project: HBase
> Issue Type: Bug
> Components: wal
> Affects Versions: 2.0.0, 1.2.0
> Reporter: stack
> Assignee: stack
> Priority: Critical
> Fix For: 2.0.0, 1.2.0
>
> Attachments: 13811.branch-1.txt, 13811.txt, HBASE-13811.testcase.patch
>
>
> I've been running ITBLLs against branch-1 around HBASE-13616 (move of
> ServerShutdownHandler to pv2). I have come across an instance of dataloss. My
> patch for HBASE-13616 was in place so can only think it the cause (but cannot
> see how). When we split the logs, we are skipping legit edits. Digging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
