I am trying to figure out how to get to a stable ignite when persistence is enabled for a data region and WAL_MODE is NONE in case of graceful shutdown.

With Respect Ignite, it was mentioned supports REPLICATED, PARTITIONED.

Can’t find it in the Ignite API, but maybe I did’t look at the right place yet.

It seems to me that EVT_CACHE_REBALANCE_OBJECT_LOADED events are coming on the backup node of their entries, and never on primary node as it should in according to the doco.

It seems to me that EVT_CACHE_REBALANCE_OBJECT_LOADED events are coming on the backup node of their entries, and never on primary node as it should in according to the doco.

We tried to use the igite semaphore to control access to resources in a cluster. At low concurrency viz. < 10 threads the semaphore seems to work as documented. However when we have 100’s of threads it the semaphore.tryAcquire(1, 100, TimeUnit.MILLISECONDS); starts taking a lot more than 100 sec. The expectation is that it will fail in 100ms. Actually we have seen it take 15, 20 or even 30 sec.

I have a .Net 8 application that uses Apache Ignite .Net v2.16. Now I’m trying to build a Java 17 app that would join the Ignite cluster of the .Net app and use the native Ignite API to programatically reset lost partitions when such a condition is detected (further described in another SO question). The Java app also uses v2.16.

I’m connecting to Ignite via JDBC 10800, and trying to INSERT a row into a table, that has three columns.

I have created a simple Apache Ignite setup that I hope to use for SQL later, but I want to construct it via the Java API for now. It is intended to be dynamic, so I can’t use a POJO class for insertion. Unfortunately, I get this warning, and stepping through the GridQueryProcessor code in a debugger reveals no obvious fixes. I suspect that part of it is that my type() call is always null (variable b, printed as b=null), but I’m not sure.

I have configured segmentationResolver, and segmentation policy specified as RESTART_JVM, and segmentationCheckFreq set to ‘0’, means check segmentation based on the topology changes.
But, this scenario is crashing.