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

Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2012/11/09 18:18:12 UTC

[jira] [Commented] (HBASE-7131) Race condition after table is re-enabled: regions are incorrectly reported as being available.

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

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

Present in 0.94 also i think.
                
> Race condition after table is re-enabled: regions are incorrectly reported as being available.
> ----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-7131
>                 URL: https://issues.apache.org/jira/browse/HBASE-7131
>             Project: HBase
>          Issue Type: Bug
>          Components: Region Assignment
>    Affects Versions: 0.96.0
>            Reporter: Aleksandr Shulman
>            Assignee: Jimmy Xiang
>         Attachments: HBase-7131-v1.patch
>
>
> For a table that is re-enabled shortly after it is disabled, regions that are reported to be online are not. This is manifested by a flush attempt throwing a NotServingRegion exception despite all regions from the original table reporting that they are online.
> I have a test in place that verifies this flaky behavior. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira