Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5DD178052 for ; Wed, 24 Aug 2011 07:12:16 +0000 (UTC) Received: (qmail 9887 invoked by uid 500); 24 Aug 2011 07:12:13 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 9303 invoked by uid 500); 24 Aug 2011 07:12:08 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 9251 invoked by uid 99); 24 Aug 2011 07:12:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Aug 2011 07:12:02 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Aug 2011 07:12:00 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 5B1F7CDE86 for ; Wed, 24 Aug 2011 07:11:36 +0000 (UTC) Date: Wed, 24 Aug 2011 07:11:36 +0000 (UTC) From: "ramkrishna.s.vasudevan (JIRA)" To: issues@hbase.apache.org Message-ID: <791287686.8502.1314169896370.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1739073306.45914.1313603787300.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-4217) HRS.closeRegion should be able to close regions with only the encoded name MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090043#comment-13090043 ] ramkrishna.s.vasudevan commented on HBASE-4217: ----------------------------------------------- @Stack Thanks for your comments. {bq} javadoc needs to better specify that what we are expecting is the encoded region name The new api is not using the encoded region name. It accepts the region name and servername. If server name is null it tries to invoke the existing closeRegion api. in The exisiting closeRegion {code} Pair pair = MetaReader.getRegion(ct, regionname); {code} If we pass the encoded region name here it is not able to retrieve the pair object. Hence i opted to get the actual region name convert to bytes, based on the servername determine which closeRegion to call.Hence the name of the new method was closeRegionByRegionName(). Pls provide your suggestions. > HRS.closeRegion should be able to close regions with only the encoded name > -------------------------------------------------------------------------- > > Key: HBASE-4217 > URL: https://issues.apache.org/jira/browse/HBASE-4217 > Project: HBase > Issue Type: Improvement > Affects Versions: 0.90.4 > Reporter: Jean-Daniel Cryans > Assignee: ramkrishna.s.vasudevan > Fix For: 0.92.0 > > Attachments: HBASE-4217.patch, HBASE-4217_1.patch > > > We had some sort of an outage this morning due to a few racks losing power, and some regions were left in the following state: > ERROR: Region UNKNOWN_REGION on sv4r17s9:60020, key=e32bbe1f48c9b3633c557dc0291b90a3, not on HDFS or in META but deployed on sv4r17s9:60020 > That region was deleted by the master but the region server never got the memo. Right now there's no way to force close it because HRS.closeRegion requires an HRI and the only way to create one is to get it from .META. which in our case doesn't contain a row for that region. Basically we have to wait until that server is dead to get rid of the region and make hbck happy. > The required change is to have closeRegion accept an encoded name in both HBA (when the RS address is provided) and HRS since it's able to find it anyways from it's list of live regions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira