hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8602) Ugly stack trace just because regionserver comes up before master....
Date Fri, 24 May 2013 07:56:36 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666084#comment-13666084
] 

Hudson commented on HBASE-8602:
-------------------------------

Integrated in hbase-0.95-on-hadoop2 #110 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/110/])
    HBASE-8602 Ugly stack trace just because regionserver comes up before master.... (Revision
1485868)

     Result = FAILURE
stack : 
Files : 
* /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java

                
> Ugly stack trace just because regionserver comes up before master....
> ---------------------------------------------------------------------
>
>                 Key: HBASE-8602
>                 URL: https://issues.apache.org/jira/browse/HBASE-8602
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.98.0, 0.95.1
>
>         Attachments: 8602.trunk.txt, 8602.txt
>
>
> I see this in the logs on simple startup:
> {code}
> 2013-03-20 10:20:00,990 WARN org.apache.hadoop.hbase.regionserver.HRegionServer: error
telling master we are up
> com.google.protobuf.ServiceException: methodName=regionServerStartup
>         at org.apache.hadoop.hbase.ipc.ProtobufRpcClientEngine$Invoker.invoke(ProtobufRpcClientEngine.java:147)
>         at com.sun.proxy.$Proxy8.regionServerStartup(Unknown Source)
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1783)
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:713)
>         at java.lang.Thread.run(Thread.java:680)
> Caused by: org.apache.hadoop.hbase.exceptions.ServerNotRunningYetException: org.apache.hadoop.hbase.exceptions.ServerNotRunningYetException:
Server is not running yet
>         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.ipc.RemoteException.instantiateException(RemoteException.java:95)
>         at org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:79)
>         at org.apache.hadoop.hbase.ipc.ProtobufRpcClientEngine$Invoker.invoke(ProtobufRpcClientEngine.java:146)
>         ... 4 more
> Caused by: org.apache.hadoop.hbase.ipc.RemoteWithExtrasException: org.apache.hadoop.hbase.exceptions.ServerNotRunningYetException:
Server is not running yet
>         at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1855)
>         at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1317)
>         at org.apache.hadoop.hbase.ipc.ProtobufRpcClientEngine$Invoker.invoke(ProtobufRpcClientEngine.java:131)
>         ... 4 more
> 2013-03-20 10:20:00,991 WARN org.apache.hadoop.hbase.regionserver.HRegionServer: reportForDuty
failed; sleeping and then retrying.
> {code}

--
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

Mime
View raw message