Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1699176558.1247699954899.JavaMail.jira@brutus>
Date: Wed, 15 Jul 2009 16:19:14 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-1662) Tool to run major compaction on
 catalog regions when hbase is shutdown
In-Reply-To: <1698020932.1247698034865.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack resolved HBASE-1662.
--------------------------

    Resolution: Fixed

Committed to branch and trunk.

> Tool to run major compaction on catalog regions when hbase is shutdown
> ----------------------------------------------------------------------
>
>                 Key: HBASE-1662
>                 URL: https://issues.apache.org/jira/browse/HBASE-1662
>             Project: Hadoop HBase
>          Issue Type: New Feature
>            Reporter: stack
>             Fix For: 0.20.0
>
>         Attachments: 1662.patch
>
>
> We need this tool in 0.19.  Mildly useful in 0.20.
> To migrate (HBASE-1215), all tables need to have had a major compaction done.    This should work fine for user-space tables as long as no writes coming in.  With catalog tables its a little different.  They will always have some edits and its tricky getting cluster to go down with it flushing -- adding more files to region.
> Am adding an HRegion#main that will list catalog region content by default -- may help debugging -- and then if you add the major_compact option, will major_compact passed region.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.