Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8D2C27B01 for ; Thu, 22 Sep 2011 04:37:34 +0000 (UTC) Received: (qmail 60081 invoked by uid 500); 22 Sep 2011 04:37:34 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 60052 invoked by uid 500); 22 Sep 2011 04:37:33 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 60040 invoked by uid 99); 22 Sep 2011 04:37:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Sep 2011 04:37:33 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ramakrishnas@huawei.com designates 119.145.14.67 as permitted sender) Received: from [119.145.14.67] (HELO szxga04-in.huawei.com) (119.145.14.67) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Sep 2011 04:37:26 +0000 Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LRW00LF6Q5SS4@szxga04-in.huawei.com> for dev@hbase.apache.org; Thu, 22 Sep 2011 12:37:04 +0800 (CST) Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LRW00KG1Q5SRQ@szxga04-in.huawei.com> for dev@hbase.apache.org; Thu, 22 Sep 2011 12:37:04 +0800 (CST) Received: from BLRNSHTIPL3NC ([10.18.1.33]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LRW004V3Q5QE8@szxml04-in.huawei.com> for dev@hbase.apache.org; Thu, 22 Sep 2011 12:37:03 +0800 (CST) Date: Thu, 22 Sep 2011 10:07:02 +0530 From: Ramkrishna S Vasudevan Subject: FW: HBCK reporting of possible mismatch in RS assignment To: dev@hbase.apache.org Reply-to: ramakrishnas@huawei.com Message-id: Organization: HTIPL MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.4862 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: Acx4aQOxVv/+6+G5TBOPV+LPK8VxKgAeDVXg X-Virus-Checked: Checked by ClamAV on apache.org Hi All Any comments on this. Best Regards Ram -----Original Message----- From: Ramkrishna S Vasudevan [mailto:ramakrishnas@huawei.com] Sent: Wednesday, September 21, 2011 7:46 PM To: dev@hbase.apache.org Subject: HBCK reporting of possible mismatch in RS assignment Hi All, I have a query regarding the report generated by HBCK. Assume there are two RS- RS1 and RS2. A region R1 is being opened in RS1. If it takes more time to open particularly in the updateMeta part. So now if the transition from OPENING to OPENED fails(due to timeout monitor reassigning) though we clear the info of this region in RS1 we do not clear the entry that was updated in Meta. So META will have an entry for RS1 hosting R1. Now the assignment of R1 to RS2 becomes successful but we have two entries in META for the same region. If we run the HBCK tool it reports an inconsistency saying region assignment in META is RS1 but actually assigned to RS2. Is this expected or we need to dig in more and make the HBCK aware of such scenarios ? Pls correct me if am not correct in my query? Best Regards Ram