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 E26807477 for ; Tue, 15 Nov 2011 07:50:54 +0000 (UTC) Received: (qmail 43365 invoked by uid 500); 15 Nov 2011 07:50:39 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 41712 invoked by uid 500); 15 Nov 2011 07:50:16 -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 41668 invoked by uid 99); 15 Nov 2011 07:50:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Nov 2011 07:50:12 +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; Tue, 15 Nov 2011 07:50:12 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id DFD3C846A1 for ; Tue, 15 Nov 2011 07:49:51 +0000 (UTC) Date: Tue, 15 Nov 2011 07:49:51 +0000 (UTC) From: "gaojinchao (Commented) (JIRA)" To: issues@hbase.apache.org Message-ID: <1443499100.30056.1321343391918.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: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-4739?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1315= 0290#comment-13150290 ]=20 gaojinchao commented on HBASE-4739: ----------------------------------- In fact, I made =E2=80=8B=E2=80=8Banother patch that is more complicated an= d is not compatible, so I didn't commit. another patch step: 1. Hmaster creater a zk node(M_ZK_REGION_PENDING_CLOSE) and set RIT to pend= ingclose state 2. send rpc to RS 3. RS change zk node to RS_ZK_REGION_CLOSING 4. Master changes RIT to closing if above steps, We can distinguish the state of RIT. if M_ZK_REGION_PENDING= _CLOSE we can send a rpc. RS_ZK_REGION_CLOSING we can add to RIT. =20 > Master dying while going to close a region can leave it in transition for= ever > -------------------------------------------------------------------------= ---- > > 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: HBASE-4739_Trunk.patch, HBASE-4739_Trunk_V2.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 did= n'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.AssignmentMan= ager: Regions in transition timed out: TestTable,0007560564,1320253568406.= f76899564cabe7e9857c3aeb526ec9dc. state=3DCLOSING, ts=3D1320253605285, serv= er=3Dsv4r11s38,62003,1320195046948 > 2011-11-03 00:02:49,130 INFO org.apache.hadoop.hbase.master.AssignmentMan= ager: 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 u= nless 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 administrato= rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp= a For more information on JIRA, see: http://www.atlassian.com/software/jira