Andreas Neumann created TEPHRA-253:
--------------------------------------
Summary: TransactionProcessorTest is sometimes flaky
Key: TEPHRA-253
URL: https://issues.apache.org/jira/browse/TEPHRA-253
Project: Tephra
Issue Type: Bug
Affects Versions: 0.12.0-incubating
Reporter: Andreas Neumann
Assignee: Poorna Chandra
The test sometimes fails as follows:
{noformat}
Running org.apache.tephra.hbase.coprocessor.TransactionProcessorTest
Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.741 sec <<<
FAILURE!
testFamilyDeleteTimestamp(org.apache.tephra.hbase.coprocessor.TransactionProcessorTest)
Time elapsed: 1.526 sec
testTransactionStateCache(org.apache.tephra.hbase.coprocessor.TransactionProcessorTest)
Time elapsed: 0.053 sec
testDataJanitorRegionScanner(org.apache.tephra.hbase.coprocessor.TransactionProcessorTest)
Time elapsed: 0.288 sec <<< FAILURE!
org.junit.internal.ArrayComparisonFailure: arrays first differed at element
[3]; expected:<4> but was:<1>
at
org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:50)
at org.junit.Assert.internalArrayEquals(Assert.java:473)
at org.junit.Assert.assertArrayEquals(Assert.java:294)
at org.junit.Assert.assertArrayEquals(Assert.java:305)
at
org.apache.tephra.hbase.coprocessor.TransactionProcessorTest.assertKeyValueMatches(TransactionProcessorTest.java:593)
at
org.apache.tephra.hbase.coprocessor.TransactionProcessorTest.assertKeyValueMatches(TransactionProcessorTest.java:585)
at
org.apache.tephra.hbase.coprocessor.TransactionProcessorTest.testDataJanitorRegionScanner(TransactionProcessorTest.java:190)
{noformat}
It is not clear what is causing this, most likely the region server did not
have an up-to-date transaction state snapshot at the time of the lfush (that
might be due to TEPHRA-239 orTEPHRA-249, or it might be a condition where
flush() has no effect because the region is already flushing,
Let's observe this and gather more information when/if it happens again.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)