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 42A0C10E1F for ; Fri, 13 Sep 2013 04:21:39 +0000 (UTC) Received: (qmail 31736 invoked by uid 500); 12 Sep 2013 21:58:47 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 23957 invoked by uid 500); 12 Sep 2013 21:51:43 -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 22960 invoked by uid 99); 12 Sep 2013 21:50:54 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Sep 2013 21:50:54 +0000 Date: Thu, 12 Sep 2013 21:50:54 +0000 (UTC) From: "Jimmy Xiang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-9480) Regions are unexpectedly made offline in certain failure conditions 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-9480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-9480: ------------------------------- Attachment: trunk-9480_v2.patch Attached v2, now the test should not be flaky any more. > Regions are unexpectedly made offline in certain failure conditions > ------------------------------------------------------------------- > > Key: HBASE-9480 > URL: https://issues.apache.org/jira/browse/HBASE-9480 > Project: HBase > Issue Type: Bug > Reporter: Devaraj Das > Assignee: Jimmy Xiang > Priority: Blocker > Fix For: 0.96.0 > > Attachments: 9480-1.txt, trunk-9480.patch, trunk-9480_v1.1.patch, trunk-9480_v1.2.patch, trunk-9480_v2.patch > > > Came across this issue (HBASE-9338 test): > 1. Client issues a request to move a region from ServerA to ServerB > 2. ServerA is compacting that region and doesn't close region immediately. In fact, it takes a while to complete the request. > 3. The master in the meantime, sends another close request. > 4. ServerA sends it a NotServingRegionException > 5. Master handles the exception, deletes the znode, and invokes regionOffline for the said region. > 6. ServerA fails to operate on ZK in the CloseRegionHandler since the node is deleted. > The region is permanently offline. > There are potentially other situations where when a RegionServer is offline and the client asks for a region move off from that server, the master makes the region offline. -- 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