writeBehind and continousQuery

Hello, When configured with (writeThrough and) writeBehind, does ignite only deliver objects to continuous query listeners after the object has been written to the persistence cache? It seems from my testing that is the case, and that it shouldn't be. Can someone point me to the source code where

Re: Can Apache Ignite 2.14.0 work without H2?

Yes it works without H2. Did you remove ignite-indexing and include ignite-calcite? What is the full stacktrace? On Thu, Nov 3, 2022 at 3:14 PM tore yang via user wrote: > I found this sentence in the 2.14.0 release note: > > *Calcite-based SQL engine is now independent of H2-based SQL engine an

Calcite engine status

Hi, When(and in what version) is Calcite SQL engine integration scheduled to be out of experimental/beta status? Has anyone here tried it out and have experiences to share? Thanks MW

Which cacheKeyConfiguration

Hi I'm wondering why there are CacheKeyConfiguration setters on both the IgniteConfiguration and the CacheConfiguration classes. Looking briefly at the code, they seem to be used differently but I can't decipher the intent. Thanks Mike

Critical System Error in ContinuousQuery processing node

Hi, When I start a continuous query listener while another client is deleting entries from the same cache, I observe the node and listener crash with this exception in the node: err=java.lang.ClassCastException: java.lang.Object cannot be cast to java.util.List at org.apache.ignite.internal.pro

"Failed to update store" cacheCriticalSize

Hi, Using GridCacheWriteBehindStore (Version 2.10.0), we are occasionally receiving this error message "Failed to update store (value will be lost as current buffer size is greater than 'cacheCriticalSize.." Looking at the code to try to determine how to raise the buffer size, I observe that 1.

Error in docs

https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/DataStorageConfiguration.html It states by setCheckpointFrequency that "If the rate is high, checkpoint will be triggered more frequently." But this is a wait period in milliseconds, so a higher number will mean less

Re: Re[2]: What does "First 10 long running cache futures" ?

In my experience, seeing the ' First 10 long running cache futures' warning (which should probably be logged as Fatal) means the ignite node your client is connected to is busted and needs to be rebooted. In addition, since ignite clients aren't smart enough to disconnect from a node in a busted st

Re: Ignite CheckpointReadLock /Long running cache futures

re detailed analysis, could you share your logs and thread dumps? > > --- > Ilya > > пн, 6 сент. 2021 г. в 22:21, Mike Wiesenberg : > >> Using Ignite 2.10.0 >> >> We had a frustrating series of issues with Ignite the other day. We're >> using

Ignite CheckpointReadLock /Long running cache futures

Using Ignite 2.10.0 We had a frustrating series of issues with Ignite the other day. We're using a 4-node cluster with 1 backup per table and cacheMode set to Partitioned, and write behind enabled. We have a client that inserts data into caches and another client that listens for new data in thos