You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2011/07/21 13:02:58 UTC

[jira] [Commented] (HBASE-3918) When assigning regions to an address, check the regionserver is actually online first

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

ramkrishna.s.vasudevan commented on HBASE-3918:
-----------------------------------------------

@Stack,
I think this one issue due to rolling restart.

Is this applicable when the cluster belongs to older version before 0.90(0.89.x) and 0.90.x versions?
When i had my RS in the 0.90 and my master in 0.91 version then the RS is not even able to read the master address string.  I think there is a change here between 0.90 and 0.91.

So my query is, is this defect applicable only between 0.89.x and 0.90.x versions?



> When assigning regions to an address, check the regionserver is actually online first
> -------------------------------------------------------------------------------------
>
>                 Key: HBASE-3918
>                 URL: https://issues.apache.org/jira/browse/HBASE-3918
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>
> This one came up in the case where the data was copied from one cluster to another.  The first cluster was running 0.89.x.  The second 0.90.x.  On startup of 0.90.x, it wanted to verify .META. was in the location -ROOT- said it was at, so it tried connect to the FIRST cluster.  The attempt failed because of mismatched RPCs.  The master then actually aborted.
> {code}
> org.apache.hadoop.hbase.ipc.HBaseRPC$VersionMismatch: Protocol org.apache.hadoop.hbase.ipc.HRegionInterface version mismatch. (client = 27, server = 24)
> at org.apache.hadoop.hbase.ipc.HBaseRPC.getProxy(HBaseRPC.java:424)
> 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:965)
> at org.apache.hadoop.hbase.catalog.CatalogTracker.getCachedConnection(CatalogTracker.java:386)
> at org.apache.hadoop.hbase.catalog.CatalogTracker.getMetaServerConnection(CatalogTracker.java:285)
> at org.apache.hadoop.hbase.catalog.CatalogTracker.verifyMetaRegionLocation(CatalogTracker.java:486)
> at org.apache.hadoop.hbase.master.HMaster.assignRootAndMeta(HMaster.java:442)
> at org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:389)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:283)
> 2011-05-23 22:38:07,720 INFO org.apache.hadoop.hbase.master.HMaster: Aborting
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira