Yu Li created HBASE-15150:
-----------------------------

             Summary: Fix TestDurablity in branch-1.1
                 Key: HBASE-15150
                 URL: https://issues.apache.org/jira/browse/HBASE-15150
             Project: HBase
          Issue Type: Bug
            Reporter: Yu Li
            Assignee: Yu Li


>From [UT 
>report|https://builds.apache.org/job/PreCommit-HBASE-Build/145/artifact/patchprocess/patch-unit-hbase-server-jdk1.7.0_79.txt]
> of HBASE-15120 against branch-1.1, we could see below failure:
{noformat}
testIncrementWithReturnResultsSetToFalse(org.apache.hadoop.hbase.regionserver.wal.TestDurability)
  Time elapsed: 0.111 sec  <<< FAILURE!
java.lang.AssertionError: expected null, but 
was:<keyvalues={row1/family:col1/1452864457248/Put/vlen=8/seqid=4}>
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.failNotNull(Assert.java:755)
        at org.junit.Assert.assertNull(Assert.java:737)
        at org.junit.Assert.assertNull(Assert.java:747)
        at 
org.apache.hadoop.hbase.regionserver.wal.TestDurability.testIncrementWithReturnResultsSetToFalse(TestDurability.java:215)
{noformat}
Checking the history, this should be a regression caused by HBASE-15031, and 
confirmed the UT could pass before commit c5cfea4e37a.

Reason of the failure is HBASE-15031 introduced the 
{{hbase.increment.fast.but.narrow.consistency}} flag which is *false* by 
default, but forget to set it in 
TestDurablity#testIncrementWithReturnResultsSetToFalse



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to