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

stack commented on HBASE-19997:
-------------------------------

>From description, item #1 maybe ok --- hbase1 can read hbase2 WALs HBASE-19166 
>-- and item #2 should be ok too.

Trying a rolling upgrade. Started a 0.98 cluster. Loaded it w/ data.

Stopped 0.98 master. Started branch-2 master. It comes up, the extant 0.98 
regionservers register. Then we get stuck on figuring hbase:meta. 
RecoverMetaProcedure seems to skip reading zk location of hbase:meta and tries 
to assign but fails w/ the below....

2018-02-23 16:49:36,252 WARN  [RSProcedureDispatcher-pool3-t2] 
procedure.RSProcedureDispatcher: Failed dispatch to 
server=ve0542.halxg.cloudera.com,60020,1519276337941 try=0
java.io.IOException: java.io.IOException
  at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2247)
  at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:104)
  at org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
  at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
  at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
  at 
org.apache.hadoop.hbase.regionserver.HRegionServer.openRegion(HRegionServer.java:3991)
  at 
org.apache.hadoop.hbase.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:20408)
  at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2195)
  ... 4 more

  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
  at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
  at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
  at 
org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.instantiateException(RemoteWithExtrasException.java:93)
  at 
org.apache.hadoop.hbase.ipc.RemoteWithExtrasException.unwrapRemoteException(RemoteWithExtrasException.java:83)
  at 
org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.makeIOExceptionOfException(ProtobufUtil.java:345)
  at 
org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:322)
  at 
org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$OpenRegionRemoteCall.sendRequest(RSProcedureDispatcher.java:389)
  at 
org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$OpenRegionRemoteCall.call(RSProcedureDispatcher.java:371)
  at 
org.apache.hadoop.hbase.master.procedure.RSProcedureDispatcher$OpenRegionRemoteCall.call(RSProcedureDispatcher.java:356)
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  at java.lang.Thread.run(Thread.java:748)

Need to figure why it can't get server from hbase:meta....





> [rolling upgrade] 1.x => 2.x
> ----------------------------
>
>                 Key: HBASE-19997
>                 URL: https://issues.apache.org/jira/browse/HBASE-19997
>             Project: HBase
>          Issue Type: Umbrella
>            Reporter: stack
>            Priority: Major
>             Fix For: 2.0.0-beta-2
>
>
> An umbrella issue of issues needed so folks can do a rolling upgrade from 
> hbase-1.x to hbase-2.x.
> (Recent) Notables:
>  * hbase-1.x can't read hbase-2.x WALs -- hbase-1.x doesn't know the 
> AsyncProtobufLogWriter class used writing the WAL -- see 
> https://issues.apache.org/jira/browse/HBASE-19166?focusedCommentId=16362897&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16362897
>  for exception.
>  ** Might be ok... means WAL split fails on an hbase1 RS... must wait till an 
> hbase-2.x RS picks up the WAL for it to be split.
>  * hbase-1 can't open regions from tables created by hbase-2; it can't find 
> the Table descriptor. See 
> https://issues.apache.org/jira/browse/HBASE-19116?focusedCommentId=16363276&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16363276
>  ** This might be ok if the tables we are doing rolling upgrade over were 
> written with hbase-1.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to