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, [email protected] < [email protected]> wrote: > 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 > for writing the key value cache. The cluster has 4 nodes with 198GB ram and > 48 cores. > > We got a similar error again and here is the error description: > > [2019-10-25 10:16:45,399][ERROR][disco-event-worker-#142][G] Blocked > system-critical thread has been detected. This can lead to cluster-wide > undefined behaviour [threadName=data-streamer-stripe-0, blockedFor=2032s] > [2019-10-25 10:16:45,399][WARN ][disco-event-worker-#142][G] Thread > [name="data-streamer-stripe-0-#49", id=80, state=WAITING, blockCnt=7, > waitCnt=5352642] > > [2019-10-25 10:16:45,399][ERROR][disco-event-worker-#142][root] Critical > system error detected. Will be handled accordingly to configured handler > [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, > super=AbstractFailureHandler [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED, > SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext > [type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker > [name=data-streamer-stripe-0, igniteInstanceName=null, finished=false, > heartbeatTs=1572010973019]]] > > Thanx and Regards, > KR Kumar > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- - Denis
