[
https://issues.apache.org/jira/browse/HBASE-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-3304:
-------------------------
Attachment: 3304-v2.txt
Exception is when we are verifying the root location at startup to see if we
should reassign root. When we go to do that, we get
ServerNotRunningException... so root can't have been assigned. Therefore,
catch this exception and return null for root not assigned... and higher up the
assignment will be dealt with.
> Get spurious master fails during bootup
> ---------------------------------------
>
> Key: HBASE-3304
> URL: https://issues.apache.org/jira/browse/HBASE-3304
> Project: HBase
> Issue Type: Bug
> Reporter: ryan rawson
> Assignee: ryan rawson
> Priority: Blocker
> Fix For: 0.90.0
>
> Attachments: 3304-v2.txt, hbase-3304.txt
>
>
> the log says:
> 2010-12-01 20:42:21,115 WARN
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
> Remove exception connecting to RS
> org.apache.hadoop.ipc.RemoteException:
> org.apache.hadoop.hbase.ipc.ServerNotRunningException: Server is not
> running yet
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1035)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:753)
> at
> org.apache.hadoop.hbase.ipc.HBaseRPC$Invoker.invoke(HBaseRPC.java:257)
> at $Proxy6.getProtocolVersion(Unknown Source)
> at org.apache.hadoop.hbase.ipc.HBaseRPC.getProxy(HBaseRPC.java:419)
> at org.apache.hadoop.hbase.ipc.HBaseRPC.getProxy(HBaseRPC.java:393)
> at org.apache.hadoop.hbase.ipc.HBaseRPC.getProxy(HBaseRPC.java:444)
> at org.apache.hadoop.hbase.ipc.HBaseRPC.waitForProxy(HBaseRPC.java:349)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getHRegionConnection(HConnectionManager.java:953)
> at
> org.apache.hadoop.hbase.catalog.CatalogTracker.getCachedConnection(CatalogTracker.java:384)
> at
> org.apache.hadoop.hbase.catalog.CatalogTracker.waitForRootServerConnection(CatalogTracker.java:210)
> at
> org.apache.hadoop.hbase.catalog.CatalogTracker.verifyRootRegionLocation(CatalogTracker.java:453)
> at
> org.apache.hadoop.hbase.master.HMaster.assignRootAndMeta(HMaster.java:421)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:379)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:274)
> 2010-12-01 20:42:21,118 FATAL org.apache.hadoop.hbase.master.HMaster:
> Unhandled exception. Starting shutdown.
> org.apache.hadoop.hbase.ipc.ServerNotRunningException:
> org.apache.hadoop.hbase.ipc.ServerNotRunningException: Server is not
> running yet
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1035)
> 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.RemoteExceptionHandler.decodeRemoteException(RemoteExceptionHandler.java:96)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getHRegionConnection(HConnectionManager.java:959)
> at
> org.apache.hadoop.hbase.catalog.CatalogTracker.getCachedConnection(CatalogTracker.java:384)
> at
> org.apache.hadoop.hbase.catalog.CatalogTracker.waitForRootServerConnection(CatalogTracker.java:210)
> at
> org.apache.hadoop.hbase.catalog.CatalogTracker.verifyRootRegionLocation(CatalogTracker.java:453)
> at
> org.apache.hadoop.hbase.master.HMaster.assignRootAndMeta(HMaster.java:421)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:379)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:274)
> 2010-12-01 20:42:21,119 INFO org.apache.hadoop.hbase.master.HMaster: Aborting
> 2010-12-01 20:42:21,119 DEBUG org.apache.hadoop.hbase.master.HMaster:
> Stopping service threads
> then the master exits. the cluster doesn't start.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
