Scaled up ignite nodes are not participating in the existing topology

user0Hhh1 0
Viewed 40

Ignite cluster was running with 3 replicas and having persistence data storage of 80 GB. Backup as one. CPU 3 cores RAM is 6 GB.

Half of the caches are created with Partitioned mode and collocated. One of this cache is loaded with 70% of data. Remaining caches are replicated.

Scaled up the ignite cluster to 5 with 10 GB RAM. All nodes were up and the newly created nodes were not participating in the existing topology.

Observed one node was using more CPU and RAM and other nodes were using very less.

Can you help us to overcome this scenario?

ignite
1 Answers

When you add nodes to a cluster with persistence enabled, you need to adjust the "baseline topology." There are multiple ways, but the easiest is to use the control.sh script:

./control.sh --baseline add consistentId1,consistentId2 --yes
Stephen Darlington0
Related