Re: The code inside the CacheEntryProcessor executes multiple times. Why?

Any feedback? 在 2021/10/14 15:03, 38797715 写道: Hi, The internal code of CacheEntryProcessor in the attachment has been executed multiple times. Why? Is there any simple way to solve this problem? package com.test; import java.util.Collections; import java.util.HashMap; import

Re: Problem with Cache KV Remote Query

Confirmed "Compact footer" setting fixed the problem. Thanks a lot. -MJ ---Original--- From: "Alex Plehanov"https://ignite.apache.org/docs/latest/data-modeling/affinity-collocation#configuring-affinity-key; . When I run the code in single jvm, it works perfect and successfully retrieved

RE: Problem with ScanQuery with filter on ClinetCache

Hi Alex, Copying the jar file worked. Thanks. - Regards, Prasad Kommoju From: Alex Plehanov Sent: Monday, October 18, 2021 2:05 PM To: user@ignite.apache.org Subject: Re: Problem with ScanQuery with filter on ClinetCache You should deploy not only the Person class, but

Re: Problem with ScanQuery with filter on ClinetCache

You should deploy not only the Person class, but also the filter class. You can, for example, make a jar with required classes and put it to the server classpath. пн, 18 окт. 2021 г. в 23:53, Prasad Kommoju : > Hi Alex, > > > > Thanks for the clarification. I am running it on a loptop, using the

RE: Problem with ScanQuery with filter on ClinetCache

Hi Alex, Thanks for the clarification. I am running it on a loptop, using the default configuration file so there is only one node and the client code and the server both run on the same laptop. Could you suggest how to deploy the Person class to other node (in production there will be) and in

Re: Problem with ScanQuery with filter on ClinetCache

Hello, Thin client doesn't have a peer class loader (and most probably will never have). To use predicates you should deploy classes for these predicates to Ignite nodes. Serializable interface for Person class will not help here. пн, 18 окт. 2021 г. в 20:14, Prasad Kommoju : > Thanks for the

RE: Problem with ScanQuery with filter on ClinetCache

Thanks for the tip but it did not help. Also, there was another suggestion that Person should implement Serializable. The examples do not show this requirement, I am going to try this too. - Regards, Prasad Kommoju From: Ilya Kazakov Sent: Sunday, October 17, 2021 8:41

RE: [EXT] Re: Crash of Ignite (B+Tree corrupted) on a large PutIfAbsent

> some changes can be already made in the DB prior to the exception Ok. Then fixing the .NET error and the documentation would be nice. From: Alex Plehanov Sent: lundi 18 octobre 2021 14:55 To: user@ignite.apache.org Subject: Re: [EXT] Re: Crash of Ignite (B+Tree corrupted) on a large

Re: Problem with Cache KV Remote Query

Hello, How was the entry inserted to the cache? You are trying to get this entry via thin client, if the entry was inserted via thick-client (Ignite node) you can face such a problem. Ignite thin-client and Ignite nodes have different default "Compact footer" property values, so POJO keys are

Re: [EXT] Re: Crash of Ignite (B+Tree corrupted) on a large PutIfAbsent

> Will you add a test in Ignite to avoid the crash I'm not quite sure, but perhaps a crash is the best we can do in this case. Throwing exception to the user might be not enough, since some changes can be already made in the DB prior to the exception and this can lead to data inconsistency. >

Ignite Cluster becomes unresponsive when relaunching client nodes

Link to stack overflow post:. We are intermittently seeing the following error on our k8tes setup. The issue happens after we relaunch our tomcat pod which launches new Ignite client

Re: Exception using ThinClient in dotnet core

Hi Stéphane, Thanks for the bug report, this issue is tracked in https://issues.apache.org/jira/browse/IGNITE-14776 On Mon, Oct 18, 2021 at 1:55 PM Stéphane Gayet wrote: > Hi community, > > I'm trying to use thin client in a net5.0 project. When running the > process, I get an error when

Exception using ThinClient in dotnet core

Hi community, I'm trying to use thin client in a net5.0 project. When running the process, I get an error when calling StartClient(). Exception":"System.ArgumentNullException: Value cannot be null. (Parameter 'logger') at Apache.Ignite.Core.Impl.Common.IgniteArgumentCheck.NotNull(Object

Re: Ignite cluster stability problems under heavy load

Hi again, We managed to stabilize heap a bit for now, by tuning some general and cache configuration: - enabled direct I/O - enabled write throttling - changed writeSynchronizationMode to FULL_ASYNC We have now 5 days without peaks in heap (stabilized at around 4GB) and GC pauses (<

Re[6]: Failed to perform cache operation (cache is stopped)

Akash, can you attach here full logs with failure, not only a part ? thanks !  >Could someone please help me out here to find out the root cause of this  >problem? >This is now happening so frequently.   >On Wed, Oct 13, 2021 at 3:56 PM Akash Shinde < akashshi...@gmail.com > wrote: >>Yes, I have