Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1848551620.1210290415657.JavaMail.jira@brutus>
Date: Thu, 8 May 2008 16:46:55 -0700 (PDT)
From: "Jim Kellerman (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-614) Retiring regions is not used; exploit
 or remove
In-Reply-To: <2141767406.1210018795630.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-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Kellerman resolved HBASE-614.
---------------------------------

    Resolution: Fixed

Retiring regions was not used, and the window in which it could be used was very small... removed.

> Retiring regions is not used; exploit or remove
> -----------------------------------------------
>
>                 Key: HBASE-614
>                 URL: https://issues.apache.org/jira/browse/HBASE-614
>             Project: Hadoop HBase
>          Issue Type: Improvement
>    Affects Versions: 0.2.0, 0.1.2
>            Reporter: stack
>            Assignee: Jim Kellerman
>             Fix For: 0.2.0
>
>
> There is a little dance around region close where a region first gets moved into the retiring queue.  The idea, IIRC, was that regions in retiring could serve reads while close was going about its business.   Meant that region was online that bit longer.
> This feature is not used any more -- regions are added to retiring but gets do not bother to look in retiring.  We should either remove retiring cocept altogether or else make use of it again.

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