You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2013/05/03 22:24:16 UTC

[jira] [Resolved] (HBASE-4794) Altering a tables that splits can hold the command for the CatalogJanitor sleep time

     [ https://issues.apache.org/jira/browse/HBASE-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans resolved HBASE-4794.
---------------------------------------

    Resolution: Invalid

Table locking takes care of this, closing.
                
> Altering a tables that splits can hold the command for the CatalogJanitor sleep time
> ------------------------------------------------------------------------------------
>
>                 Key: HBASE-4794
>                 URL: https://issues.apache.org/jira/browse/HBASE-4794
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.0
>            Reporter: Jean-Daniel Cryans
>             Fix For: 0.92.3
>
>
> In AssignmentManager.getReopenStatus, it calls a version of MetaReader.getTableRegions that sets excludeOfflinedSplitParents to false meaning that the offline parents are returned. What this means is that if one of them was already closed before the alter command was issued (and I believe there are a few other cases) then the alter will hang until the CatalogJanitor sweeps the parent .META. row.
> Since the CJ sleep time is 5 minutes, the worst case scenario is an alter that takes almost 5 minutes.
> Here's an example:
> {quote}
> 925/948 regions updated.
> 920/943 regions updated.
> 913/934 regions updated.
> 912/928 regions updated.
> 912/928 regions updated.
> (5 minutes later)
> 912/928 regions updated.
> 912/928 regions updated.
> 905/918 regions updated.
> 897/906 regions updated.
> 891/892 regions updated.
> 891/891 regions updated.
> Done.
> {quote}
> I can confirm with the log that 37 parent regions were cleaned up.
> Also it's pretty nice to see how the number fluctuates up and down :)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira