hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3918) When assigning regions to an address, check the regionserver is actually online first
Date Wed, 27 Jul 2011 14:59:09 GMT

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

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

@Stack.
{noformat}
This one came up in the case where the data was copied from one cluster to another
{noformat}
How was this copying done? Is it through replication?  I have a doubt here
In this link 'http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/replication/package-summary.html#requirements'
I found a requirement like 
{noformat}
Both clusters should have the same HBase and Hadoop major revision. For example, having 0.90.1
on the master and 0.90.0 on the slave is correct but not 0.90.1 and 0.89.20100725.
{noformat}
So how can i first copy the data from 0.89 version to 0.90.  Sorry if my query is very basic?
Am not aware of replication.  

> 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

        

Mime
View raw message