You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Bill Graham (JIRA)" <ji...@apache.org> on 2011/01/24 08:24:43 UTC
[jira] Commented: (HBASE-3406) Region stuck in transition after RS
failed while opening
[ https://issues.apache.org/jira/browse/HBASE-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985543#action_12985543 ]
Bill Graham commented on HBASE-3406:
------------------------------------
I got myself into the same state. I was able to do this using 0.90.0-rc1 and CDH3b2 by either:
- Changing COMPRESSION => 'lzo' on an existing table where lzo is not set up on HBase.
- Creating a new table with COMPRESSION => 'lzo' where lzo is not set up on HBase.
In my case though hbck -fix wouldn't work. I had to restart the cluster and then run hbck -fix. See this thread for more info:
http://mail-archives.apache.org/mod_mbox/hbase-user/201101.mbox/%3CAANLkTi=GRWBhOVM=YjKMODfm8XyVN5T0XEkdb4FF2CrP@mail.gmail.com%3E
> Region stuck in transition after RS failed while opening
> --------------------------------------------------------
>
> Key: HBASE-3406
> URL: https://issues.apache.org/jira/browse/HBASE-3406
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.0
> Reporter: Todd Lipcon
> Priority: Critical
> Fix For: 0.90.1
>
>
> I had a RS fail due to GC pause while it was in the midst of opening a region, apparently. This got the region stuck in the following repeating sequence in the master log:
> 2011-01-03 17:24:33,884 INFO org.apache.hadoop.hbase.master.AssignmentManager: Region has been OPENING for too long, reassigning region=usertable,user991629466,1293747979500.c6a54b4d07a44e113b3a4d2ab22daa70.
> 2011-01-03 17:24:33,885 DEBUG org.apache.hadoop.hbase.zookeeper.ZKUtil: master:60000-0x12ce26f6c0600e3 Retrieved 113 byte(s) of data from znode /hbase/unassigned/c6a54b4d07a44e113b3a4d2ab22daa70; data=region=usertable,user991629466,1293747979500.c6a54b4d07a44e113b3a4d2ab22daa70., server=haus03.sf.cloudera.com:60000, state=M_ZK_REGION_OFFLINE
> 2011-01-03 17:24:43,886 INFO org.apache.hadoop.hbase.master.AssignmentManager: Regions in transition timed out: usertable,user991629466,1293747979500.c6a54b4d07a44e113b3a4d2ab22daa70. state=OPENING, ts=1293840977790
> 2011-01-03 17:24:43,886 INFO org.apache.hadoop.hbase.master.AssignmentManager: Region has been OPENING for too long, reassigning region=usertable,user991629466,1293747979500.c6a54b4d07a44e113b3a4d2ab22daa70.
> 2011-01-03 17:24:43,887 DEBUG org.apache.hadoop.hbase.zookeeper.ZKUtil: master:60000-0x12ce26f6c0600e3 Retrieved 113 byte(s) of data from znode /hbase/unassigned/c6a54b4d07a44e113b3a4d2ab22daa70; data=region=usertable,user991629466,1293747979500.c6a54b4d07a44e113b3a4d2ab22daa70., server=haus03.sf.cloudera.com:60000, state=M_ZK_REGION_OFFLINE
> etc... repeating every 10 seconds. Eventually I ran hbck -fix which forced it to OFFLINE in ZK and it reassigned just fine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.