Re: JDBC Connection Pooling

Hi All, If I use client connection configuration to set the number of threads for a JDBC connection, and use the connection with multiple insert statements (with streaming set to true), to multiple different caches, are the inserts stacked because the connection is shared? Should I create

Re: JDBC Connection Pooling

Hi On Thu, Apr 16, 2020 at 12:33 PM Evgenii Zhuravlev wrote: > As I said, if you use only DataStreamer, without jdbc, just a plain, > key-value IgniteDataStreamer, then, you should have only one instance per > cache. It will give you the better performance. This one streamer can be > used from

Re: Random2LruPageEvictionTracker causing hanging in our integration tests

out.multipart-aa out.multipart-ab out.multipart-ac

Re: Apache ignite evolvable object

Hi, BinaryObjects allow doing this: https://apacheignite.readme.io/docs/binary-marshaller Evgenii пт, 1 мая 2020 г. в 09:03, Hemambara : > I am using apache ignite 2.8.0. Looking for an option to have evolvable > data > model similar to coherence (com.tangosol.io.Evolvable). Do we have any ? >

Apache ignite evolvable object

I am using apache ignite 2.8.0. Looking for an option to have evolvable data model similar to coherence (com.tangosol.io.Evolvable). Do we have any ? Idea is to save future data if the domain model version is backward compatible and when the same model is transferred to new version, we can

Re: Event Listners when we use DataStreamer

Hello! We have a test for this in our code base, org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest#testFlushTimeout It passes in 2.8. Do you have a reproducer where you don't see EVT_CACHE_OBJECT_PUT for cache populated by data streamer with allowOverride(true)? Can

Re: Cluster went down after "Unable to await partitions release latch within timeout" WARN

Hi Pavel, The exchange finished taking its time, but during that time, new client was not able to write to the cache. So what happened was that There were 4 Ignite servers out of a bunch of 19 (as you can see in the consistentids) in my message above, that their acknowledgement to Coordinator

Re: Cluster went down after "Unable to await partitions release latch within timeout" WARN

Hello, I don't clearly understand from your message, but have the exchange finally finished? Or you were getting this WARN message all the time? пт, 1 мая 2020 г. в 12:32, Ilya Kasnacheev : > Hello! > > This description sounds like a typical hanging Partition Map Exchange, but > you should be

Re: Event Listners when we use DataStreamer

Hi Ilya - I have tried that but not firing the event. But it does fire for put and putAll Thanx and Regards, KR Kumar -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Random2LruPageEvictionTracker causing hanging in our integration tests

Hello! Yes, you are right, I happened to miss the relevant portion. Do you see any "Too many attempts to choose data page" or "Too many failed attempts to evict page" messages in your logs? How large are your data regions, how many caches do they have? I would expect that behavior if eviction

Re: Cluster went down after "Unable to await partitions release latch within timeout" WARN

Hello! This description sounds like a typical hanging Partition Map Exchange, but you should be able to see that in logs. If you don't, you can collect thread dumps from all nodes with jstack and check it for any stalling operations (or share with us). Regards, -- Ilya Kasnacheev пт, 1 мая

Re: Re: Backups not being done for SQL caches

Hi Alexandr, Thanks, I didn't know the metrics and topology info was different. I found the issue, we were not adding the nodes to the baseline topology due to a bug. We're using v2.8.0 in the upgrade/migration, previous version is 2.7 Regards, Courtney Robinson Founder and CEO, Hypi Tel: ++44

Re: Cluster went down after "Unable to await partitions release latch within timeout" WARN

Hi Pavel, I am using 2.8 and still getting the same issue. Here is the ecosystem 19 Ignite servers (S1 to S19) running at 16GB of max JVM and in persistent mode. 96 Clients (C1 to C96) There are 19 machines, 1 Ignite server is started on 1 machine. The clients are evenly distributed across