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

Hudson commented on HBASE-6160:
-------------------------------

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #42 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/42/])
    HBASE-6160 META entries from daughters can be deleted before parent entries 
(Revision 1346496)

     Result = FAILURE
stack : 
Files : 
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/CatalogJanitor.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestCatalogJanitor.java

                
> META entries from daughters can be deleted before parent entries
> ----------------------------------------------------------------
>
>                 Key: HBASE-6160
>                 URL: https://issues.apache.org/jira/browse/HBASE-6160
>             Project: HBase
>          Issue Type: Bug
>          Components: client, regionserver
>    Affects Versions: 0.92.2, 0.94.0, 0.96.0
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 0.92.2, 0.94.1
>
>         Attachments: HBASE-6160_v1.patch, HBASE-6160_v2.patch, 
> HBASE-6160_v2.patch, HBASE-6160v2092.txt
>
>
> HBASE-5986 fixed and issue, where the client sees the META entry for the 
> parent, but not the children. However, after the fix, we have seen the 
> following issue in tests: 
> Region A is split to -> B, C
> Region B is split to -> D, E
> After some time, META entry for B is deleted since it is not needed anymore, 
> but META entry for Region A stays in META (C still refers it). In this case, 
> the client throws RegionOfflineException for B. 

--
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

        

Reply via email to