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 6AE197804 for ; Tue, 1 Nov 2011 06:09:01 +0000 (UTC) Received: (qmail 64432 invoked by uid 500); 1 Nov 2011 06:09:01 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 64261 invoked by uid 500); 1 Nov 2011 06:08:56 -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 64247 invoked by uid 99); 1 Nov 2011 06:08:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2011 06:08:55 +0000 X-ASF-Spam-Status: No, hits=-2001.2 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; Tue, 01 Nov 2011 06:08:53 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 3B6A032B4FA for ; Tue, 1 Nov 2011 06:08:32 +0000 (UTC) Date: Tue, 1 Nov 2011 06:08:32 +0000 (UTC) From: "ramkrishna.s.vasudevan (Commented) (JIRA)" To: issues@hbase.apache.org Message-ID: <131152121.44743.1320127712244.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1566574206.2498.1314605978865.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-4277) 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 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140968#comment-13140968 ] ramkrishna.s.vasudevan commented on HBASE-4277: ----------------------------------------------- Tests passes... {code} testClockSkewDetection(org.apache.hadoop.hbase.master.TestClockSkewDetection): hostname can't be null testScanner(org.apache.hadoop.hbase.regionserver.TestScanner): hostname can't be null {code} This failure is not due to the patch for this JIRA. > HRS.closeRegion should be able to close regions with only the encoded name > -------------------------------------------------------------------------- > > Key: HBASE-4277 > URL: https://issues.apache.org/jira/browse/HBASE-4277 > Project: HBase > Issue Type: Bug > Affects Versions: 0.90.4 > Reporter: ramkrishna.s.vasudevan > Assignee: ramkrishna.s.vasudevan > Priority: Critical > Fix For: 0.90.5 > > Attachments: HBASE-4277_0.90.patch > > > As suggested by Stack in HBASE-4217 creating a new issue to provide a patch for 0.90.x version. > 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. > bq.If a 0.90 version, we maybe should do that in another issue. -- 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