[
https://issues.apache.org/jira/browse/HBASE-29161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933487#comment-17933487
]
Duo Zhang commented on HBASE-29161:
-----------------------------------
Rolling upgrading with replication enabled succeeded.
I've set up two clusters, init test table on both clusters with command
{noformat}
./bin/hbase ltt -init_only -compression SNAPPY -tn test_ns:test_tn
-num_regions_per_server 20
{noformat}
And then on the source cluster, alter table to set replication scope and add a
replication peer
{noformat}
alter "test_ns:test_tn", { NAME => "test_cf", REPLICATION_SCOPE => "1"}
add_peer "1", CLUSTER_KEY => "meta01,meta02,meta03:2181:/hbase2", NAMESPACES =>
["test_ns"]
{noformat}
And then run ltt on source cluster
{noformat}
./bin/hbase ltt -write 4:1024 -num_keys 10000000 -tn test_ns:test_tn -skip_init
{noformat}
At the same time, I rolling upgraded master and then region server of source
cluster to 3.0.0-beta-2, the ltt finished without any error.
And then I used ltt read to verify the result on both source and peer cluster
{noformat}
./bin/hbase ltt -read 100 -num_keys 10000000 -tn test_ns:test_tn
{noformat}
LTT finished without any error.
During the rolling upgrading, the replication peer was disabled so there were
some replication delay. This is by design since we need to migrate the
replication queue data from zookeeper to hbse:replication table. But after all
region servers have been upgraded, the migration procedure will enable the peer
again and there is no data loss.
> Test rolling upgrading from 2.x to 3.0.0
> ----------------------------------------
>
> Key: HBASE-29161
> URL: https://issues.apache.org/jira/browse/HBASE-29161
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
>
> At least we should test rolling upgrading from 2.6.x, with some changed
> features like region replication and replication enabled, to see if the
> migration works as expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
