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 824A89C4B for ; Wed, 23 Nov 2011 01:05:03 +0000 (UTC) Received: (qmail 63561 invoked by uid 500); 23 Nov 2011 01:05:03 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 63535 invoked by uid 500); 23 Nov 2011 01:05:03 -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 63524 invoked by uid 99); 23 Nov 2011 01:05:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Nov 2011 01:05:03 +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; Wed, 23 Nov 2011 01:05:00 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id E9EF1981AB for ; Wed, 23 Nov 2011 01:04:39 +0000 (UTC) Date: Wed, 23 Nov 2011 01:04:39 +0000 (UTC) From: "gaojinchao (Commented) (JIRA)" To: issues@hbase.apache.org Message-ID: <1408756805.4707.1322010279959.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1554445905.56557.1320342093142.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-4739) Master dying while going to close a region can leave it in transition forever 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-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155600#comment-13155600 ] gaojinchao commented on HBASE-4739: ----------------------------------- @Ted It seems 0.90.5 logic is ok. 1. if RS_ZK_REGION_CLOSING is created, It says that RS has received the RPC 2. When RIT is timeout, There is two case, one RS is slow, in this case we don't need send RPC again. another case, closing the region has exception, we send rpc can't solve the problem, it may also fail. So I think we don't need fix anything. > Master dying while going to close a region can leave it in transition forever > ----------------------------------------------------------------------------- > > Key: HBASE-4739 > URL: https://issues.apache.org/jira/browse/HBASE-4739 > Project: HBase > Issue Type: Bug > Affects Versions: 0.90.4 > Reporter: Jean-Daniel Cryans > Assignee: gaojinchao > Priority: Minor > Fix For: 0.92.0, 0.94.0, 0.90.5 > > Attachments: 4739_trial2.patch, 4739_trialV3.patch, HBASE-4739_Trunk.patch, HBASE-4739_Trunk_V2.patch, HBASE-4739_trail5.patch, HBASE-4739_trial.patch, HBASE-4739_trial6.patch > > > I saw this in the aftermath of HBASE-4729 on a 0.92 refreshed yesterday, when the master died it had just created the RIT znode for a region but didn't tell the RS to close it yet. > When the master restarted it saw the znode and started printing this: > {quote} > 2011-11-03 00:02:49,130 INFO org.apache.hadoop.hbase.master.AssignmentManager: Regions in transition timed out: TestTable,0007560564,1320253568406.f76899564cabe7e9857c3aeb526ec9dc. state=CLOSING, ts=1320253605285, server=sv4r11s38,62003,1320195046948 > 2011-11-03 00:02:49,130 INFO org.apache.hadoop.hbase.master.AssignmentManager: Region has been CLOSING for too long, this should eventually complete or the server will expire, doing nothing > {quote} > It's never going to happen, and it's blocking balancing. > I'm marking this as minor since I believe this situation is pretty rare unless you hit other bugs while trying out stuff to root bugs out. -- 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