Hi,
This means that both of your nodes have a different baseline. This was
most likely due to activation after a node restart.
The right way:
1) Start two new nodes (with clean PDS)
2) Activate the cluster - after that both nodes will be in the baseline
3) If your nodes crash, just restart them. Do not use activation
anymore. The cluster will be activated when all nodes from the baseline
are online.
If you need to add new nodes to the baseline or remove it from the
baseline, you can use the related API:
https://apacheignite.readme.io/docs/baseline-topology#setting-the-topology-from-code
https://apacheignite.readme.io/docs/baseline-topology#setting-the-topology-from-command-line
BR,
Andrei
12/8/2020 7:49 AM, rakshita04 пишет:
Hi Team,
We are using baseline topology concept for our two nodes, running on
separate machines.
We are getting below error when both of these nodes run together-
Caused by: class org.apache.ignite.spi.IgniteSpiException: BaselineTopology
of joining node (DSU_B) is not compatible with BaselineTopology in the
cluster. Branching history of cluster BlT ([65356776]) doesn't contain
branching point hash of joining node BlT (65356777). Consider cleaning
persistent storage of the node and adding it to the cluster again.
After getting this error , when we deleted the nodes and restarted ignite.
it worked fine.
But this way we are loosing our data.
We are using similar configuration.xml file for both of them.
What can we do to avoid this issue?
regards,
Rakshita Chaudhary
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
