[
https://issues.apache.org/jira/browse/HBASE-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289585#comment-13289585
]
stack commented on HBASE-6160:
------------------------------
@Ram Yes, the father was split and his children subsequently compacted and let
go of references so he was removed but his no-good brother was still around...
with references probably so the ancestor could not yet be cleared. The
RegionOfflineException is because of the fix over in HBASE-5986.
Yes, we still need to prioritize references files. I'd think that the no-good
brother would eventually compact away his references making the great
grandfather removable. Why would this patch change compactions or the rate at
which regions are removed from .META. Ram? (I can see removals perhaps going a
little slower, more lumpy, but otherwise, should be as it is now)?
> 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
> Attachments: HBASE-6160_v1.patch
>
>
> 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
