apache / apache/ignite

BaselineTopology of joining node (47cf4755-484a-438c-9a83-e8984eab05b3) is not compatible with BaselineTopology in the cluster

Open
#12,582 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
5.1k
Forks
1.9k
Avg merge
3d 2h
Merged PRs (30d)
46

Description

How to fix BaselineTopology of joining node ERROR?

Ignite Version = 2.16.0
Running Ignite Single Node with Springboot. once backend start ignite automatic start with that.
where Springboot Version: 127.0.0.1 and Java Version: 21

We are migrating ignite work directory from AWS Server to Proxmox Server(where file system is ZFS)
In AWS Server application is working on those data. after after migrated ingite throwing following error.

Ignite Error Log :
```
Caused by: org.apache.ignite.IgniteCheckedException: Failed to start SPI: TcpDiscoverySpi [addrRslvr=null, addressFilter=null, sockTimeout=5000, ackTimeout=5000, marsh=JdkMarshaller [clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@517013b3], reconCnt=10, reconDelay=2000, maxAckTimeout=600000, soLinger=0, forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null, skipAddrsRandomization=false]
at org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:280)
at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:1076)
at org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1774)
... 47 common frames omitted
Caused by: org.apache.ignite.spi.IgniteSpiException: BaselineTopology of joining node (47cf4755-484a-438c-9a83-e8984eab05b3) is not compatible with BaselineTopology in the cluster. Branching history of cluster BlT ([439122630]) doesn't contain branching point hash of joining node BlT (-609359374). 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:2110)
at org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:1204)
at org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:472)
at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2206)
at org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:277)
... 49 common frames omitted
```

Java Code :
```
@Configuration
public class IgniteInit {

/**
* This method is used to create ignite bean
*
* @return {@link Ignite}
*/
@Bean
public Ignite getIgnite() {
return IgniteConfig.getIgnite();
}
}

public class IgniteConfig {

private static final String DFM_IGNITE_SERVER_XML = "dfm_ignite-server.xml";

public static Ignite getIgnite() {
if (ignite == null) {
synchronized (IgniteConfig.class) {
if (ignite == null) {
try {
ignite = Ignition.start(DFM_IGNITE_SERVER_XML);
loadData(ignite);
} catch (Exception e) {
LOGGER.error(e.getMessage());
LOGGER.error("Unexpected failure: %s\n", e);
}

} else {
try {
Collection cacheNames = ignite.cacheNames();
LOGGER.debug("cacheNames : " + cacheNames);
} catch (Exception e) {
try {
ignite.close();
} catch (Exception e1) {
e1.printStackTrace();
}
ignite = Ignition.start(DFM_IGNITE_SERVER_XML);
loadData(ignite);
}
}
}
}
// LOGGER.debug("ignite : " + ignite);
return ignite;
}

/**
* This method is used to load previous data
*
* @param ignite
*/
private static void loadData(Ignite ignite) {
LOGGER.info(">>> Loading cache ");
ignite.cluster().state(ClusterState.ACTIVE);

ignite.cache(IgniteConstant.PERMISSION_CACHE).loadCache(null);

ignite.cache(IgniteConstant.OBJECT_TYPE_CACHE).loadCache(null);

ignite.cache(IgniteConstant.OBJECT_CACHE).loadCache(null);
}
...............
}
```
ignite xml config :
```







DFM





























































127.0.0.1:47500..47510

















.......................

Contributor guide

Open the contributing guide

Research direction

Start with the reported stack frames in org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi and ServerImpl, then review the configured persistent storage, WAL, and workDirectory paths in dfm_ignite-server.xml. The issue does not define a repository change, reproduction steps, or acceptance test, so a completed fix is not identifiable from the report alone.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot
Domain
databases, distributed-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.