This message actually looks worrisome:
2019-10-22 10:31:42,441][WARN
][data-streamer-stripe-3-#52][PageMemoryImpl] Parking
thread=data-streamer-stripe-3-#52 for timeout (ms)=771038
It means that Ignite's throttling algorithm has decided to put a thread to
sleep for 771 seconds.
Can you share
Have you tried to turn of the failure handling following the previously
shared documentation page? It looks like some timeouts need to be tuned.
Denis
On Friday, October 25, 2019, krkumar24061...@gmail.com <
krkumar24061...@gmail.com> wrote:
> Hi - The application is doing two things, one
Hi - The application is doing two things, one thread is writing 2kb size
events to the ignite cache as a key value and other thread is executing
ignite SQLs thru ignite jdbc connections. The throughput is anything between
25K to 40K events per second on the cache size. We are using data streamer
Hi,
What is the application doing while you are changing the topology? Is the
cluster under the load?
Generally, we've added critical failure handlers in the latest version of
Ignite and the message reported is printed out by them:
https://apacheignite.readme.io/docs/critical-failures-handling
Hi guys - I am running into the following issue when trying to add a node
to the baseline topology? Its happening only after we had upgraded from 2.3
to 2.75. Any pointers would be appreciated.
2019-10-22 10:31:42,441][WARN ][data-streamer-stripe-3-#52][PageMemoryImpl]
Parking
