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 31F4618588 for ; Tue, 18 Aug 2015 10:16:47 +0000 (UTC) Received: (qmail 82373 invoked by uid 500); 18 Aug 2015 10:16:46 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 81616 invoked by uid 500); 18 Aug 2015 10:16:46 -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 81603 invoked by uid 99); 18 Aug 2015 10:16:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Aug 2015 10:16:45 +0000 Date: Tue, 18 Aug 2015 10:16:45 +0000 (UTC) From: "Liu Shaohui (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-14237) Meta region may be onlined on multi regonservers for bugs of assigning meta MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Liu Shaohui created HBASE-14237: ----------------------------------- Summary: Meta region may be onlined on multi regonservers for bugs of assigning meta Key: HBASE-14237 URL: https://issues.apache.org/jira/browse/HBASE-14237 Project: HBase Issue Type: Bug Affects Versions: 0.94.11 Reporter: Liu Shaohui Assignee: Liu Shaohui Priority: Critical When a regionserver failed to open the meta region and crash after setting the RS_ZK_REGION_FAILED_OPEN state of meta region in zookeeper, the master will handle the event of RS_ZK_REGION_FAILED_OPEN and try to assign the meta region again in AssignmentManager#handleRegion. But at the same time, the master will handle the regionserver expired event and start a MetaServerShutdownHandler for the regionserver, because the servername of regionserver is same as the servername of the unassigned node of meta region. In the MetaServerShutdownHandler, the meta region may be assigned for second time. [~heliangliang] We have encountered this problem in our production cluster which resulted in inconsistency of region location in meta table. You can see the log from the attachment. The code of AssignmentManager is so complex and I have not get a solution to fix this problem. Could someone kindly help to give some suggestions? Thanks -- This message was sent by Atlassian JIRA (v6.3.4#6332)