hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5986) Clients can see holes in the META table when regions are being split
Date Fri, 11 May 2012 01:11:48 GMT

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

Lars Hofhansl commented on HBASE-5986:
--------------------------------------

True, META is not single region by design, but effectively it is (not really suggesting that
we add more code that relies on this). I think you're right we could add a split policy that
ensures that parent and daughters are always in the same region.

As for the alternative:
If the client has to recheck in these (rare) cases that seems OK, as long as the client can
reliably tell that it does have to recheck.

                
> Clients can see holes in the META table when regions are being split
> --------------------------------------------------------------------
>
>                 Key: HBASE-5986
>                 URL: https://issues.apache.org/jira/browse/HBASE-5986
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.1, 0.96.0, 0.94.1
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>         Attachments: HBASE-5986-test_v1.patch
>
>
> We found this issue when running large scale ingestion tests for HBASE-5754. The problem
is that the .META. table updates are not atomic while splitting a region. In SplitTransaction,
there is a time lap between the marking the parent offline, and adding of daughters to the
META table. This can result in clients using MetaScanner, of HTable.getStartEndKeys (used
by the TableInputFormat) missing regions which are made just offline, but the daughters are
not added yet. 
> This is also related to HBASE-4335. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message