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

Andrew Purtell commented on HBASE-18233:
----------------------------------------

With this change applied TestMultiParallel will flake

[ERROR] Tests run: 13, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 17.641 
s <<< FAILURE! - in org.apache.hadoop.hbase.client.TestMultiParallel
[ERROR] 
testMultiThreadWithRowLocks(org.apache.hadoop.hbase.client.TestMultiParallel)  
Time elapsed: 5.487 s  <<< FAILURE!
java.lang.AssertionError
        at 
org.apache.hadoop.hbase.client.TestMultiParallel.testMultiThreadWithRowLocks(TestMultiParallel.java:898)

I don't see it when running the test on its own, but if large tests are 
executed with enough parallelism, the above failure shows up. I didn't see it 
before this change, but I can't say for certain. I'm sorry, I wish I could be 
more definitive. I'm running the test in a loop 100 times to see if it will 
flake on its own even if it's the only thing on the CPU at the time.

> We shouldn't wait for readlock in doMiniBatchMutation in case of deadlock
> -------------------------------------------------------------------------
>
>                 Key: HBASE-18233
>                 URL: https://issues.apache.org/jira/browse/HBASE-18233
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.2.7
>            Reporter: Allan Yang
>            Assignee: Allan Yang
>            Priority: Blocker
>             Fix For: 1.4.0, 1.3.2, 1.2.7
>
>         Attachments: HBASE-18233-branch-1.2.patch, 
> HBASE-18233-branch-1.2.trivial.patch, HBASE-18233-branch-1.2.v2.patch, 
> HBASE-18233-branch-1.2.v3.patch, HBASE-18233-branch-1.2.v4 (1).patch, 
> HBASE-18233-branch-1.2.v4 (1).patch, HBASE-18233-branch-1.2.v4 (2).patch, 
> HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, 
> HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, 
> HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, 
> HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, 
> HBASE-18233-branch-1.2.v5 (1).patch, HBASE-18233-branch-1.2.v5.patch, 
> HBASE-18233-branch-1.2.v5.patch, HBASE-18233-branch-1.2.v6.patch, 
> HBASE-18233.branch-1.2.UT.log, HBASE-18233.branch-1.3.001.patch, 
> HBASE-18233.branch-1.3.001.patch, HBASE-18233.branch-1.3.002.patch, 
> HBASE-18233.branch-1.3.002.patch, HBASE-18233.branch-1.3.003.patch, 
> HBASE-18233.branch-1.3.003.patch, HBASE-18233.branch-1.4.001.patch, 
> HBASE-18233.branch-1.4.002.patch, HBASE-18233.branch-1.4.002.patch
>
>
> Please refer to the discuss in HBASE-18144
> https://issues.apache.org/jira/browse/HBASE-18144?focusedCommentId=16051701&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16051701



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to