[
https://issues.apache.org/jira/browse/HBASE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091419#comment-13091419
]
Jean-Daniel Cryans commented on HBASE-4238:
-------------------------------------------
Another way this problem appears is if the 2 daughters are removed from parent
and one of them was split and already cleaned before the CJ went to delete the
parent, this will fail (CJ.cleanParent):
{code}
if ((a.getFirst() && !a.getSecond()) && (b.getFirst() && !b.getSecond())) {
{code}
Here we check if the directory of each daughter exists and if they don't have a
reference. In my case, they don't exist since they were already cleaned, which
means that the parent will _never_ get cleaned.
> CatalogJanitor can clear a daughter that split before processing its parent
> ---------------------------------------------------------------------------
>
> Key: HBASE-4238
> URL: https://issues.apache.org/jira/browse/HBASE-4238
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.4
> Reporter: Jean-Daniel Cryans
> Priority: Critical
> Fix For: 0.90.5
>
>
> I didn't dig a lot into this issue, but by splitting a table twice in a row I
> was able to trigger a situation where a daughter of the first split was
> deleted by the CatalogJanitor before it processed its parent. Will post log
> in a comment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
