hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13811) Splitting WALs, we are filtering out too many edits -> DATALOSS
Date Wed, 03 Jun 2015 04:48:50 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570273#comment-14570273
] 

Duo Zhang commented on HBASE-13811:
-----------------------------------

Yeah, with the patch in place
{code}
	    for (;;) {
	      RegionStoreSequenceIds ids =
	          testUtil.getMiniHBaseCluster().getMaster().getServerManager()
	              .getLastFlushedSequenceId(region.getRegionInfo().getEncodedNameAsBytes());
	      if (ids.getStoreSequenceId(0).getSequenceId() > oldestSeqIdOfStore) {
	        break;
	      }
	      Thread.sleep(100);
	    }
{code}

This will not happen so the testcase does not quit...Let me see...

> 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)

Mime
View raw message