[
https://issues.apache.org/jira/browse/HBASE-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468353#comment-13468353
]
stack commented on HBASE-6316:
------------------------------
Trying it, there are a few issues. Here is one:
{code}
2012-10-02 22:13:55,804 WARN
org.apache.hadoop.hbase.regionserver.HRegionServer: error telling master we are
up
com.google.protobuf.ServiceException:
org.apache.hadoop.hbase.ipc.ServerNotRunningYetException:
org.apache.hadoop.hbase.ipc.ServerNotRunningYetException: Server is not running
yet
at
org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:188)
at $Proxy10.regionServerStartup(Unknown Source)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:2009)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:848)
at java.lang.Thread.run(Thread.java:680)
Caused by: org.apache.hadoop.hbase.ipc.ServerNotRunningYetException:
org.apache.hadoop.hbase.ipc.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.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:187)
... 4 more
Caused by: org.apache.hadoop.ipc.RemoteException:
org.apache.hadoop.hbase.ipc.ServerNotRunningYetException: Server is not running
yet
at
org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1798)
at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1300)
at
org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:178)
... 4 more
{code}
Ugly. Not end of world.
This seems longer than it should be:
{code}
2012-10-02 22:13:57,095 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting for region servers count to settle; currently checked in 0, slept for
1537 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms,
interval of 1500 ms.
2012-10-02 22:13:58,629 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting for region servers count to settle; currently checked in 0, slept for
3071 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms,
interval of 1500 ms.
2012-10-02 22:13:58,808 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Attempting connect to
Master server at pynchon,60961,1349241221417
2012-10-02 22:13:58,808 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Connected to master at
pynchon/192.168.1.74:60961
2012-10-02 22:13:58,808 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Telling master at
pynchon,60961,1349241221417 that we are up with port=60964,
startcode=1349241229036
{code}
This is broke on local filesystem:
{code}
Caused by: java.io.IOException: mark/reset not supported
at org.apache.hadoop.fs.FSInputChecker.reset(FSInputChecker.java:418)
at java.io.FilterInputStream.reset(FilterInputStream.java:200)
at org.apache.hadoop.hbase.io.Reference.parseFrom(Reference.java:233)
at org.apache.hadoop.hbase.io.Reference.read(Reference.java:180)
at
org.apache.hadoop.hbase.regionserver.StoreFile.<init>(StoreFile.java:259)
at org.apache.hadoop.hbase.regionserver.HStore$1.call(HStore.java:415)
at org.apache.hadoop.hbase.regionserver.HStore$1.call(HStore.java:413)
{code}
Thats enough for now
> Confirm can upgrade to 0.96 from 0.94 by just stopping and restarting
> ---------------------------------------------------------------------
>
> Key: HBASE-6316
> URL: https://issues.apache.org/jira/browse/HBASE-6316
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Blocker
> Fix For: 0.96.0
>
>
> Over in HBASE-6294, LarsH says you have to currently clear zk to get a 0.96
> to start over data written by a 0.94. Need to fix it so don't have to do
> this -- that zk state left over gets auto-migrated.
--
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
