[jira] [Commented] (HBASE-11834) TestHRegionBusyWait.testParallelAppendWithMemStoreFlush fails sporadically

["ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org>]

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

ramkrishna.s.vasudevan commented on HBASE-11834:
------------------------------------------------

Stack,
It was me who introduced this.  I have one suggestion here
{code}
long flushSeqId = getNextSequenceId(wal);
{code}
could throw an exception.  So not releasing the lock in finally would again be a problem?  I wanted to release the lock in finally but was not right. So release it in the existing finally.
{code}
  if (w != null) {
          mvcc.advanceMemstore(w);
        }
{code}


> TestHRegionBusyWait.testParallelAppendWithMemStoreFlush fails sporadically
> --------------------------------------------------------------------------
>
>                 Key: HBASE-11834
>                 URL: https://issues.apache.org/jira/browse/HBASE-11834
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: stack
>            Assignee: stack
>         Attachments: 11834.txt
>
>
> See https://builds.apache.org/view/H-L/view/HBase/job/HBase-TRUNK/5431/testReport/junit/org.apache.hadoop.hbase.regionserver/TestHRegionBusyWait/testParallelAppendWithMemStoreFlush/
> Fails locally for me regularly.  TIming.  Turns out that on if we go to flush and no edits to flush, we can take the update lock and not release it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)