Re: Another replicated cache oddity

2023-11-21 Thread Zhenya Stanilovsky via user
  >Hi,   Hi, this really looks like very strange  First of all you need to check consistency of your data : [1]   > Some time ago an element (E) was added to this cache (among many others) And some time it will be all ok there ? Are you sure that this element was properly touched ?  What king of

Another replicated cache oddity

2023-11-21 Thread Raymond Wilson
Hi, We have been triaging an odd issue we encountered in a system using Ignite v2.15 and the C# client. We have a replicated cache across four nodes, lets call them P0, P1, P2 & P3. Because the cache is replicated every item added to the cache is present in each of P0, P1, P2 and P3. Some time

Continuous queries, Exactly Once

2023-11-21 Thread Adam Augusta
For a ContinuousQuery, the documentation indicates that the local listener is guaranteed exactly once delivery of each event. This is very appealing to me, as I’d like to construct a continuous debezium-style changelog of the cache. But I’m having difficulty pinning down a guarantee that every

Why are there so many of "Client disconnected abruptly due to network connection loss...." in the log?

2023-11-21 Thread zc
Hello Ignite community. I started three ignite nodes, but after a while, there are a lot of the following content : Line 20658: [17:07:01,115][WARNING][grid-nio-worker-client-listener-0-#33][ClientListenerProcessor] Client disconnected abruptly due to network connection loss or because the