We have recently encountered the following:
Caused by: org.apache.ignite.spi.IgniteSpiException: BaselineTopology of
joining node (404d8988-6c2d-4612-ab17-fde635b9da8f) is not compatible with
BaselineTopology in the cluster.
Branching history of cluster BlT ([-205608975, 383765073, 1797002251,
-1091313502]) doesn't contain branching point hash of joining node BlT
(-1295062797). Consider cleaning persistent storage of the node and adding it
to the cluster again.
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:1946)
~[stormjar.jar:?]
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:969)
~[stormjar.jar:?]
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:391)
~[stormjar.jar:?]
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2020)
~[stormjar.jar:?]
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
~[stormjar.jar:?]
... 41 more
We were running a cluster with 4 nodes. Each node in the cluster has a couple
of LOCAL caches, there are currently no replicated/partitioned caches. Looking
at
https://cwiki.apache.org/confluence/display/IGNITE/Automatic+activation+design+-+draft,
it seems that this can happen when "there are different versions of the same
data". However, since we have only LOCAL caches, I'm not sure how that could
happen. So a couple of questions:
1. Why does this happen for our use case? How is the "branching point hash" of
a node calculated?
2. Is there any documentation that talks about BaselineTopology in depth,
including versioning/branching history?
3. As I mentioned, we are currently relying on LOCAL caches. The reason that we
are doing this is that we don't have a need for the caches to be distributed
across processes at this point, but still want the off-heap/persistence
functionality, and potentially will have client nodes for a given server node
as well.
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist
shows that there are plans to remove LOCAL caches in Ignite 3.0. Since they are
being deprecated, is there an equivalent way to achieve isolated caches with
PARTITIONED/REPLICATED caches? If number of partitions is 1 and number of
backups is 0, is this the same thing?
