You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (Commented) (JIRA)" <ji...@apache.org> on 2011/11/16 16:04:51 UTC

[jira] [Commented] (HBASE-4799) Catalog Janitor logic bug causes region leackage

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

Ted Yu commented on HBASE-4799:
-------------------------------

Max:
Please use the following command to generate patch so that HadoopQA can run tests for it:
{code}
git format-patch --no-prefix HEAD^:HEAD
{code}
Please attach temporary fix patch first, formal patch second - HadoopQA would pick up the latest patch.

After that, please click 'Submit Patch' to run tests on Jenkins.

Thanks for the patch.

If you experienced this problem in your cluster, please tell us whether the fix worked.
                
> Catalog Janitor logic bug causes region leackage
> ------------------------------------------------
>
>                 Key: HBASE-4799
>                 URL: https://issues.apache.org/jira/browse/HBASE-4799
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.90.4
>            Reporter: Max Lapan
>            Assignee: Max Lapan
>            Priority: Critical
>         Attachments: 0001-Fix-of-Regions-Leaks-problem-in-janitor.patch, 0002-Temporary-fix-to-remove-leaked-regions.patch
>
>
> When region split takes a significant amount of time, CatalogJanitor can cleanup one of SPLIT records, but left another in META. When another split finish, janitor cleans left SPLIT record, but parent regions haven't removed from FS and META not cleared.
> The race condition is follows:
> 1. region split started
> 2. one of regions splitted, i.e. A (have no reference storefiles) but other (B) doesn't
> 3. janitor started and in routine checkDaughter removes SPLITA from meta, but see that SPLITB has references and does nothing.
> 4. region B completes split
> 5. janitor wakes up, removes SPLITB, but see that there is no records for A and does nothing again.
> Result - parent region hangs forever.

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