Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 16 Nov 2011 00:23:51 +0000 (UTC)
From: "Jean-Daniel Cryans (Created) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <708857857.33284.1321403031518.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HBASE-4794) Altering a tables that splits can
 hold the command for the CatalogJanitor sleep time
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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
            Priority: Critical
             Fix For: 0.92.0, 0.94.0


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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira