Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <28636477.69731288050020014.JavaMail.jira@thor>
Date: Mon, 25 Oct 2010 19:40:20 -0400 (EDT)
From: "HBase Review Board (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Commented: (HBASE-3147) Regions stuck in transition after
 rolling restart, perpetual timeout handling but nothing happens
In-Reply-To: <11401629.50871287959058930.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HBASE-3147?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1292=
4784#action_12924784 ]=20

HBase Review Board commented on HBASE-3147:
-------------------------------------------

Message from: "Jonathan Gray" <jgray@apache.org>

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.cloudera.org/r/1087/#review1662
-----------------------------------------------------------

Ship it!


Looks good.  Not sure if I can +1 my patch but I think we should commit :)


trunk/src/main/java/org/apache/hadoop/hbase/master/ServerManager.java
<http://review.cloudera.org/r/1087/#comment5542>

    Should we remove this code from inside of ServerShutdownHandler now?  N=
ot a big deal but being done twice.


- Jonathan


> Regions stuck in transition after rolling restart, perpetual timeout hand=
ling but nothing happens
> -------------------------------------------------------------------------=
------------------------
>
>                 Key: HBASE-3147
>                 URL: https://issues.apache.org/jira/browse/HBASE-3147
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>             Fix For: 0.90.0
>
>
> The rolling restart script is great for bringing on the weird stuff.  On =
my little loaded cluster if I run it, it horks the cluster and it doesn't r=
ecover.  I notice two issues that need fixing:
> 1. We'll miss noticing that a server was carrying .META. and it never get=
s assigned -- the shutdown handlers get stuck in perpetual wait on a .META.=
 assign that will never happen.
> 2. Perpetual cycling of the this sequence per region not succesfully assi=
gned:
> {code}
>  2010-10-23 21:37:57,404 INFO org.apache.hadoop.hbase.master.AssignmentMa=
nager: Regions in transition timed out:  usertable,user510588360,1287547556=
587.7f2d92497d2d03917afd574ea2aca55b. state=3DPENDING_OPEN,                =
       ts=3D1287869814294  45154 2010-10-23 21:37:57,404 INFO org.apache.ha=
doop.hbase.master.AssignmentManager: Region has been PENDING_OPEN or OPENIN=
G for too long, reassigning region=3Dusertable,user510588360,1287547556587.=
                                     7f2d92497d2d03917afd574ea2aca55b.  451=
55 2010-10-23 21:37:57,404 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign=
: master:60000-0x2bd57d1475046a Attempting to transition node 7f2d92497d2d0=
3917afd574ea2aca55b from RS_ZK_REGION_OPENING to M_ZK_REGION_OFFLINE  45156=
 2010-10-23 21:37:57,404 WARN org.apache.hadoop.hbase.zookeeper.ZKAssign: m=
aster:60000-0x2bd57d1475046a Attempt to transition the unassigned node for =
7f2d92497d2d03917afd574ea2aca55b from RS_ZK_REGION_OPENING to              =
   M_ZK_REGION_OFFLINE failed, the node existed but was in the state M_ZK_R=
EGION_OFFLINE  45157 2010-10-23 21:37:57,404 INFO org.apache.hadoop.hbase.m=
aster.AssignmentManager: Region transitioned OPENING to OFFLINE so skipping=
 timeout, region=3Dusertable,user510588360,1287547556587.7f2d92497d2d03917a=
fd574ea2aca55b. =20
> ,,,
> {code}
> Timeout period again elapses an then same sequence.
> This is what I've been working on.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.