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 F0B75F2D9 for ; Thu, 4 Apr 2013 20:10:15 +0000 (UTC) Received: (qmail 92675 invoked by uid 500); 4 Apr 2013 20:10:15 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 92623 invoked by uid 500); 4 Apr 2013 20:10:15 -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 92614 invoked by uid 99); 4 Apr 2013 20:10:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Apr 2013 20:10:15 +0000 Date: Thu, 4 Apr 2013 20:10:15 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8266) Master cannot start if TableNotFoundException is thrown while partial table recovery 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-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622727#comment-13622727 ] Ted Yu commented on HBASE-8266: ------------------------------- {code} + } catch (KeeperException e) { + // Keeper exception should not happen here {code} Add a log in the catch block ? {code} + throw new TableNotFoundException(tableNameStr); + } else { {code} The 'else' keyword can be omitted. > Master cannot start if TableNotFoundException is thrown while partial table recovery > ------------------------------------------------------------------------------------ > > Key: HBASE-8266 > URL: https://issues.apache.org/jira/browse/HBASE-8266 > Project: HBase > Issue Type: Bug > Affects Versions: 0.95.0, 0.94.6 > Reporter: ramkrishna.s.vasudevan > Assignee: ramkrishna.s.vasudevan > Priority: Critical > Fix For: 0.95.0, 0.98.0, 0.94.7 > > Attachments: HBASE-8266.patch > > > I was trying to create a table. The table creation failed > {code} > java.io.IOException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Could not instantiate a region instance. > at org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:133) > at org.apache.hadoop.hbase.master.handler.CreateTableHandler.handleCreateHdfsRegions(CreateTableHandler.java:256) > at org.apache.hadoop.hbase.master.handler.CreateTableHandler.handleCreateTable(CreateTableHandler.java:204) > at org.apache.hadoop.hbase.master.handler.CreateTableHandler.process(CreateTableHandler.java:153) > at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:130) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Could not instantiate a region instance. > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) > at java.util.concurrent.FutureTask.get(FutureTask.java:83) > at org.apache.hadoop.hbase.util.ModifyRegionUtils.createRegions(ModifyRegionUtils.java:126) > ... 7 more > Caused by: java.lang.IllegalStateException: Could not instantiate a region instance. > at org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3765) > at org.apache.hadoop.hbase.regionserver.HRegion.createHRegion(HRegion.java:3870) > at org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:106) > at org.apache.hadoop.hbase.util.ModifyRegionUtils$1.call(ModifyRegionUtils.java:103) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > ... 3 more > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:3762) > ... 11 more > Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/hbase/CompoundConfiguration$1 > at org.apache.hadoop.hbase.CompoundConfiguration.add(CompoundConfiguration.java:82) > at org.apache.hadoop.hbase.regionserver.HRegion.(HRegion.java:438) > at org.apache.hadoop.hbase.regionserver.HRegion.(HRegion.java:401) > ... 16 more > {code} > Am not sure of the above failure. The same setup is able to create new tables. > Now the table is already in ENABLING state. The master was restarted. > Now as the table was found in ENABLING state but not added to META the EnableTableHandler > {code} > 2013-04-03 18:33:03,850 FATAL org.apache.hadoop.hbase.master.HMaster: Unhandled exception. Starting shutdown. > org.apache.hadoop.hbase.exceptions.TableNotFoundException: TestTable > at org.apache.hadoop.hbase.master.handler.EnableTableHandler.prepare(EnableTableHandler.java:89) > at org.apache.hadoop.hbase.master.AssignmentManager.recoverTableInEnablingState(AssignmentManager.java:2586) > at org.apache.hadoop.hbase.master.AssignmentManager.joinCluster(AssignmentManager.java:390) > at org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:777) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:522) > at java.lang.Thread.run(Thread.java:662) > 2013-04-03 18:33:03,880 INFO org.apache.hadoop.hbase.master.HMaster: Aborting > {code} > This does not allow me to start my master further leading to unoperationable state of the whole cluster. -- 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