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 - Denis On Tue, Oct 22, 2019 at 7:57 AM KR Kumar <[email protected]> wrote: > 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 > thread=data-streamer-stripe-3-#52 for timeout > (ms)=771038 > [2019-10-22 10:31:45,635][ERROR][tcp-disco-msg-worker-#2][G] Blocked > system-critical thread has been detected. This can lead to cluster-wide > undefined behaviour [threadName=data-streamer-stripe-30, blockedFor=95s] > [2019-10-22 10:31:45,635][WARN ][tcp-disco-msg-worker-#2][G] Thread > [name="data-streamer-stripe-30-#79", id=110, state=TIMED_WAITING, > blockCnt=0, waitCnt=36470] > > [2019-10-22 10:31:45,637][ERROR][tcp-disco-msg-worker-#2][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-30, igniteInstanceName=null, finished=false, > heartbeatTs=1571754609956]]] > class org.apache.ignite.IgniteException: GridWorker > [name=data-streamer-stripe-30, igniteInstanceName=null, finished=false, > heartbeatTs=1571754609956] > > Thanx and Regards, > KR Kumar >
