You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/07/17 20:06:15 UTC

[jira] Created: (HBASE-1668) hbase-1609 broke TestHRegion.testScanSplitOnRegion unit test

hbase-1609 broke TestHRegion.testScanSplitOnRegion unit test
------------------------------------------------------------

                 Key: HBASE-1668
                 URL: https://issues.apache.org/jira/browse/HBASE-1668
             Project: Hadoop HBase
          Issue Type: Bug
            Reporter: stack


testScanSplitOnRegion was test added to fix hbase-810, puts happening while an outstanding scanner and then a split.  We used to wait on the scanner to finish so was possibility of deadlock.  We no longer wait so this condition that we fixed no longer happens.  I'm going to just remove the test since whats happening now is that on split, the concurrent puts are just failing with NSRE, which is what you'd expect if a split under them.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (HBASE-1668) hbase-1609 broke TestHRegion.testScanSplitOnRegion unit test

Posted by "stack (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/HBASE-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-1668.
--------------------------

       Resolution: Fixed
    Fix Version/s: 0.20.0
         Assignee: stack

Committed.  Small change so didn't get review.

> hbase-1609 broke TestHRegion.testScanSplitOnRegion unit test
> ------------------------------------------------------------
>
>                 Key: HBASE-1668
>                 URL: https://issues.apache.org/jira/browse/HBASE-1668
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.20.0
>
>
> testScanSplitOnRegion was test added to fix hbase-810, puts happening while an outstanding scanner and then a split.  We used to wait on the scanner to finish so was possibility of deadlock.  We no longer wait so this condition that we fixed no longer happens.  I'm going to just remove the test since whats happening now is that on split, the concurrent puts are just failing with NSRE, which is what you'd expect if a split under them.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.