[
https://issues.apache.org/jira/browse/HBASE-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289277#comment-13289277
]
ramkrishna.s.vasudevan edited comment on HBASE-6160 at 6/5/12 9:21 AM:
-----------------------------------------------------------------------
@Enis
The great grandfather should have ideally been compacted right, so that it does
not have reference files, because he was the one who got splitted first. But
the father's reference files got cleared/compacted thus leading to this
problem. Correct me if am wrong?
@Stack
Do we still need to prioritize the reference files so that compaction of ref
files surely happen? So i think after this patch still the reference file of
the great grand father may not get compacted and we may never allow the CJ to
remove the entry from META? Correct me if am wrong Stack?
was (Author: ram_krish):
+1 on patch.
@Enis
The great grandfather should have ideally been compacted right, so that it does
not have reference files, because he was the one who got splitted first. But
the father's reference files got cleared/compacted thus leading to this
problem. Correct me if am wrong?
@Stack
Do we still need to prioritize the reference files so that compaction of ref
files surely happen? So i think after this patch still the reference file of
the great grand father may not get compacted and we may never allow the CJ to
remove the entry from META? Correct me if am wrong Stack?
> 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
