Hello! This is a new features and one which often misfires, see https://apacheignite.readme.io/docs/critical-failures-handling
Other than what is described, increasing failureDetectionTimeout often helps. Regards, -- Ilya Kasnacheev вт, 19 мар. 2019 г. в 16:34, Philip Wu <[email protected]>: > Hi, recently we upgraded Ignite from 2.5 to 2.7, got the following error. > > Is this configurational, or known bug in 2.7? > > > 2019-03-18 15:44:23,383 SEVERE [ (tcp-disco-msg-worker-#2%XXXGrid%)] > Critical system error detected. Will be handled accordingly to configured > handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, > super=AbstractFailureHandler > [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], > failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class > o.a.i.IgniteException: GridWorker [name=grid-nio-worker-tcp-comm-9, > igniteInstanceName=XXXGrid, finished=false, heartbeatTs=1552941767243]]]: > class org.apache.ignite.IgniteException: GridWorker > [name=grid-nio-worker-tcp-comm-9, igniteInstanceName=XXXGrid, > finished=false, heartbeatTs=1552941767243] > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
