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 2E4C310ABE for ; Tue, 6 Aug 2013 16:36:57 +0000 (UTC) Received: (qmail 82647 invoked by uid 500); 6 Aug 2013 16:36:55 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 82536 invoked by uid 500); 6 Aug 2013 16:36:53 -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 82314 invoked by uid 99); 6 Aug 2013 16:36:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Aug 2013 16:36:52 +0000 Date: Tue, 6 Aug 2013 16:36:52 +0000 (UTC) From: "Anoop Sam John (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-8627) HBCK can not fix meta not assigned issue 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-8627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-8627: ---------------------------------- Status: Open (was: Patch Available) > HBCK can not fix meta not assigned issue > ---------------------------------------- > > Key: HBASE-8627 > URL: https://issues.apache.org/jira/browse/HBASE-8627 > Project: HBase > Issue Type: Bug > Components: hbck > Affects Versions: 0.95.0 > Reporter: Anoop Sam John > Assignee: Anoop Sam John > Attachments: HBASE-8627_Trunk.patch > > > When meta table region is not assigned to any RS, HBCK run will get exception. I can see code added in checkMetaRegion() to solve this issue but it wont work. It still refers to ROOT region! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira