May we see more log Vladimir? My guess is that the reason for the failed Master instantiation shows earlier in the log. St.Ack
On Wed, Jul 3, 2013 at 10:51 AM, Vladimir Rodionov <[email protected]>wrote: > I know that sometimes its not straightforward "instantiate and run" > exercise. May be somebody has experience of troubleshooting > MiniHBaseCluster on Mac OSX (10.7.5): > > I can not start cluster: > > 2013-07-02 23:01:44,387 IPC Server handler 0 on 56830 INFO [audit] > allowed=true ugi=vrodionov (auth:SIMPLE) ip=/127.0.0.1 > cmd=listStatus src=/user/vrodionov/hbase/.archive dst=null > perm=null > 2013-07-02 23:02:03,483 main ERROR [MiniHBaseCluster] Error starting > cluster > java.lang.RuntimeException: Master not initialized after 200 seconds > at > org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:206) > at > org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:420) > at > org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:216) > at > org.apache.hadoop.hbase.MiniHBaseCluster.<init>(MiniHBaseCluster.java:86) > at > org.apache.hadoop.hbase.MiniHBaseCluster.<init>(MiniHBaseCluster.java:77) > at > org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:657) > at > org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:627) > at > org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:575) > at > org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:562) > at > com.inclouds.hbase.test.CoprocessorLoadTest.setUp(CoprocessorLoadTest.java:43) > at junit.framework.TestCase.runBare(TestCase.java:128) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:120) > at junit.framework.TestSuite.runTest(TestSuite.java:230) > at junit.framework.TestSuite.run(TestSuite.java:225) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:79) > at > org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46) > at > org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > 2013-07-02 23:02:03,484 main INFO [HMaster] Cluster shutdown requested > > > Best regards, > Vladimir Rodionov > Principal Platform Engineer > Carrier IQ, www.carrieriq.com > e-mail: [email protected] > > ________________________________________ > From: Chris Trezzo (JIRA) [[email protected]] > Sent: Wednesday, July 03, 2013 10:50 AM > To: [email protected] > Subject: [jira] [Created] (HBASE-8861) Remove ReplicaitonState completely > > Chris Trezzo created HBASE-8861: > ----------------------------------- > > Summary: Remove ReplicaitonState completely > Key: HBASE-8861 > URL: https://issues.apache.org/jira/browse/HBASE-8861 > Project: HBase > Issue Type: Improvement > Components: Replication > Affects Versions: 0.95.2 > Reporter: Chris Trezzo > > > The stop/start replication functionality is confusing. More times then not > a user really only wants to stop/start replication on a peer by peer basis. > Enable/disable peer handles this need. > > Removing ReplicationState and the admin commands associated with it will > simplify the code without losing any major functionality. > > This JIRA was created based on a discussion in HBASE-8844. > > -- > 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 > > Confidentiality Notice: The information contained in this message, > including any attachments hereto, may be confidential and is intended to be > read only by the individual or entity to whom this message is addressed. If > the reader of this message is not the intended recipient or an agent or > designee of the intended recipient, please note that any review, use, > disclosure or distribution of this message or its attachments, in any form, > is strictly prohibited. If you have received this message in error, please > immediately notify the sender and/or [email protected] and > delete or destroy any copy of this message and its attachments. >
