[
https://issues.apache.org/jira/browse/HBASE-18596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371107#comment-16371107
]
stack commented on HBASE-18596:
-------------------------------
Trying this, yeah, a 1.2 seems to replicate fine to a 2.x cluster. The 1.2
cluster wanted to create the remote table else I saw the below complaint:
{code}
ERROR: Table 98 exists in peer cluster 1, but the table descriptors are not
same when compared with source cluster. Thus can not enable the table's
replication switch.
{code}
I need to see more what it was objecting too.
I did not seem to be able to replicate from hbase2 to hbase1... would hang at
least on enable_table_replication. Let me see if can make it work if table
already created... maybe not given table state is not in zk.
> [TEST] A hbase1 cluster should be able to replicate to a hbase2 cluster;
> verify
> -------------------------------------------------------------------------------
>
> Key: HBASE-18596
> URL: https://issues.apache.org/jira/browse/HBASE-18596
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Assignee: Esteban Gutierrez
> Priority: Blocker
> Fix For: 2.0.0-beta-2
>
>
> From the mailing list thread "[DISCUSS] hbase-2.0.0 compatibility
> expectations", [~esteban] asks:
> bq. Should we add additional details around replication as well? for
> instance, shall we consider a hbase-1.x cluster as a client for a hbase-2.x
> cluster?
> The latter should be a blocker. Verify it works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
