[
https://issues.apache.org/jira/browse/HBASE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105852#comment-13105852
]
ramkrishna.s.vasudevan commented on HBASE-4238:
-----------------------------------------------
{code}
- // We will fail!!! Because split b is empty, which is right... we should
- // not remove parent if daughters do not exist in fs.
- assertFalse(janitor.cleanParent(parent, r));
- // Put in place daughter dir for b... that should make it so parent gets
- // cleaned up.
- storedir = Store.getStoreHomedir(tabledir, splitb.getEncodedName(),
- htd.getColumnFamilies()[0].getName());
{code}
This part of code is removed. Not the one in the previous comment. :)
> 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
> Assignee: stack
> Priority: Critical
> Fix For: 0.92.0, 0.90.5
>
> Attachments: 4238-v2.txt, 4238.txt
>
>
> 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
