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

Jonathan Hsieh commented on HBASE-13531:
----------------------------------------

With this patch applied (thus never using the mob feature in 
TestAcidGuarantees) I had 40 clean runs in a row.

{code}
diff --git 
a/hbase-server/src/test/java/org/apache/hadoop/hbase/TestAcidGuarantees.java 
b/hbase-server/src/test/java/org/apache/hadoop/hbase/TestAcidGuarantees.java
index dbb6156..64320ab 100644
--- a/hbase-server/src/test/java/org/apache/hadoop/hbase/TestAcidGuarantees.java
+++ b/hbase-server/src/test/java/org/apache/hadoop/hbase/TestAcidGuarantees.java
@@ -392,7 +392,7 @@ public class TestAcidGuarantees implements Tool {
     util.startMiniCluster(1);
     try {
       boolean systemTest = false;
-      boolean useMob = true;
+      boolean useMob = false; // true;
       runTestAtomicity(20000, 5, 5, 0, 3, systemTest, useMob);
     } finally {
       util.shutdownMiniCluster();
@@ -404,7 +404,7 @@ public class TestAcidGuarantees implements Tool {
     util.startMiniCluster(1);
     try {
       boolean systemTest = false;
-      boolean useMob = true;
+      boolean useMob = false; //  true;
       runTestAtomicity(20000, 5, 0, 5, 3, systemTest, useMob);
     } finally {
       util.shutdownMiniCluster();
@@ -416,7 +416,7 @@ public class TestAcidGuarantees implements Tool {
     util.startMiniCluster(1);
     try {
       boolean systemTest = false;
-      boolean useMob = true;
+      boolean useMob = false; // true;
       runTestAtomicity(20000, 5, 2, 2, 3, systemTest, useMob);
     } finally {
       util.shutdownMiniCluster();
{code}

Also, running the IT test version without useMob=false does not encounter the 
acid violation.   I'm pretty convinced it is a legit bug and due to the mob 
path.

> After 4/18/15 merge, flakey failures of 
> TestAcidGuarantees#testMobScanAtomicity
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-13531
>                 URL: https://issues.apache.org/jira/browse/HBASE-13531
>             Project: HBase
>          Issue Type: Sub-task
>          Components: regionserver, Scanners
>    Affects Versions: hbase-11339
>            Reporter: Jonathan Hsieh
>             Fix For: hbase-11339
>
>
> After the merge of master from 4/18/15 with hbase-11339 branch, we encounter 
> some atomicity violations.  We want to fix before calling merge to trunk.



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

Reply via email to