Background:
I need to migrate my data from 1 cloud service provider to another, and I pick the solution of add new nodes in current cluster, wait for data copy and rebalance and separate them into 2 clusters.
But after I took the steps below, I met a [CoordinationStateRejectedException], am I missed up some steps here?
Source cluster:
Sys: 8C16G CentOS 7 * 8
ES: 7.4.0
Cluster:
2 master nodes (master: true, data: false)
6 data nodes (master: false, data: true)
Data:
3 billion doc took over 300 GB
Indices: 6 (12s 1r, about 50~60GB per index)
Dest cluster:
Sys: 8C16G CentOS 7 * 8
ES: 7.8.0
Cluster:
2 master nodes (master: true, data: false)
6 data nodes (master: false, data: true)
My steps:
- put the master nodes in
discovery.seed_hosts
in each nodes of dest cluster
discovery.seed_hosts: ["source cluster master1", "source cluster master2", "dest cluster master1", "dest cluster master2", "dest cluster data1"...]
cluster.initial_master_nodes:["dest cluster master1", "dest cluster master2"]
- start the nodes in dest cluster and wait for their joint success
- change the settings of indices
number_of_replicas: 3
- wait for all replicas ready
- remove the master ip in source cluster from
discovery.seed_hosts
and add the dest cluster's master nodes' ip incluster.initial_master_nodes
in each of nodes of dest cluster
discovery.seed_hosts: ["dest cluster master1", "dest cluster master2", "dest cluster data1"...]
cluster.initial_master_nodes:["dest cluster master1", "dest cluster master2"]
- restart the nodes in dest cluster
But I met the [CoordinationStateRejectedException] here
org.elasticsearch.transport.RemoteTransportException: [dest-node-33][dest-node:9300][internal:cluster/coordination/join/validate]
Caused by: org.elasticsearch.cluster.coordination.CoordinationStateRejectedException: join validation on cluster state with a different cluster uuid HAlwyQ3lQ8CDIDj1KpUF1Q than local cluster uuid gqStYPHkRQqKhUGdsfRFuA, rejecting
One of the master in dest cluster started success, but all the data nodes can't join the "new" cluster then, do we have solutions on this scenario?