Failing client node due to not receiving metrics updates-IGNITE-10354

Hi, There is a cluster of four server nodes and six client nodes in production. I was using ignite 2.6.0 version and all six client nodes were failing with below error WARN o.a.i.s.d.tcp.TcpDiscoverySpi - Failing client node due to not receiving metrics updates from client node within

RE: Ignite crashed with CorruptedTreeException

Hi Ivan, Maksim, Here is the reproducer: import org.apache.ignite.Ignition; import org.apache.ignite.binary.BinaryObject; import org.apache.ignite.binary.BinaryObjectBuilder; import org.apache.ignite.cache.QueryEntity; import org.apache.ignite.client.ClientCache; import

Bug in GridCacheWriteBehindStore

There's a bug in GridCacheWriteBehindStore in the flusher method. https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheWriteBehindStore.java#L674 The logic states there that if flush thread count is not a power of 2,

Re: Ignite crashed with CorruptedTreeException

Hi Marcus! Could you please provide a complete code that inserts data (either it is SQL, or cache put, which types do you use, etc.). I've tried to reproduce your case but failed. Thanks a lot! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Programmatically triggering of write behind

Hello! You may call org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore#forceFlush when deciding to evict some entries, assuming you are doing it manually. Regards, -- Ilya Kasnacheev ср, 9 июн. 2021 г. в 11:21, r_s : > Hello All, > I am running a partitioned cache

Re: Sorting result of ScanQuery

Hello! It sounds like you need some data normalization plus SQL secondary indexes. Regards, -- Ilya Kasnacheev чт, 3 июн. 2021 г. в 17:11, Taner Ilyazov : > That's my concern. Because the requirements I have is persisting an Object > with a complex nested structure, which can't be changed. I

Re: getOrCreateCache hangs when cacheStore uses spring resources

Hello! This may obviously happen when your Ignite instance is a Spring bean, but its cache store depends on Spring context. You need to obtain Spring context but it is still under construction since Ignite is still being initialized. Make sure that cache is created only after Spring context is

Re: Clients got disconnected during the endurance testing

Hello! This may happen if your cluster has a long PME and connection pool is exhausted. You need to check server nodes' logs for suspicious messages. Regards, -- Ilya Kasnacheev чт, 3 июн. 2021 г. в 10:35, Naveen : > HI All > > We are using Ignite 2.8.1 and carrying the endurance test

Re: Ignite crashed with CorruptedTreeException

I mean that you have accidentally insert string key, not UUID. During insertion, ignite checks types of key during updating index B+ tree and this check currently lead to CorruptedTreeException. ср, 9 июн. 2021 г. в 17:37, Ivan Daschinsky : > > Hi Marcus. Yes, it is a bug on ignite, but I suppose

Re: AtomicReference issue with different userVersions

Hello! Is this a bug which needs to be addressed? If so, can you file a ticket against Ignite JIRA? Thanks, -- Ilya Kasnacheev ср, 9 июн. 2021 г. в 11:19, tanshuai : > < > http://apache-ignite-users.70518.x6.nabble.com/file/t3172/20210609161010.jpg> > > > I may have found the root cause. > >

Re: Peer ClassLoading Issue | Apache Ignite 2.10 with Spring Boot 2.3

Hello! The "Failed to resolve class name" error also looks like the https://issues.apache.org/jira/browse/IGNITE-14856 Regards, -- Ilya Kasnacheev вс, 9 мая 2021 г. в 08:28, : > Hi, > > > > We are trying to use ignite for the first time in our project. We are > trying to use ignite with

Re: ignite server restarted after Critical system error detected.

Hello! Caused by: com.datastax.driver.core.exceptions.InvalidQueryException: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING Sounds pretty

Re: Ignite throws "Failed to resolve class name" Exception

Hello! I can see a very similar issue filed: https://issues.apache.org/jira/browse/IGNITE-14856 There are hopes that it gets addresses in 2.11 Regards, -- Ilya Kasnacheev чт, 3 июн. 2021 г. в 14:37, Aleksandr Shapkin : > Hello! > > It seems that you are trying to deploy DTO using peer class

Re: Ignite crashed with CorruptedTreeException

Hi Marcus. Yes, it is a bug on ignite, but I suppose that you insert UUID instead of String Here is the actual cause of CorruptedTreeException: Caused by: java.lang.UnsupportedOperationException: Value type doesn't match: exp=20, act=13 at

Re: Programmatically triggering of write behind

Hi Alexey, thank you for your answer, this confirms what I expected. For clarification: I do not want my DB to evict any entries, I just want to make sure alle updates on the cache entries are written before the entries are removed from the cache. I have not designed the architecture of

Re: Programmatically triggering of write behind

Cache expiry policy evicts entries only from the cache and native persistent store: the external DB is not modified. So your expiry policy has nothing to do with write-behind. If you want to evict entries from both the cache and external DB you may consider implementing such a policy as a

Programmatically triggering of write behind

Hello All, I am running a partitioned cache with native persistence and write-behind to a DB. Because the DB is fairly slow, I decided to use write-behind not write-through. Out of many, mainly performance reasons it makes sense to also use native persistence instead of only in memory caching. In

Re: AtomicReference issue with different userVersions

I may have found the root cause. The invocation chain should be something like the one below. org.apache.ignite.internal.managers.deployment.GridDeploymentManager#deploy