Hello! With NoOp handler this should be a purely cosmetic message.
Regards, -- Ilya Kasnacheev чт, 21 мар. 2019 г. в 18:15, Philip Wu <[email protected]>: > Thanks, llya! > > Actually it happened in PROD system again last night ... even with > NoOpFailureHandler. > > I am rolling back to Ignite 2.5 or 2.6 for now. Thanks! > > 2019-03-20 22:28:45,044 SEVERE [ (tcp-disco-msg-worker-#2%XXXGrid%)] > Critical system error detected. Will be handled accordingly to configured > handler [hnd=NoOpFailureHandler [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-1, igniteInstanceName=XXXGrid, > finished=false, heartbeatTs=1553137996031]]]: class > org.apache.ignite.IgniteException: GridWorker > [name=grid-nio-worker-tcp-comm-1, igniteInstanceName=XXXGrid, > finished=false, heartbeatTs=1553137996031] > at > > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1831) > at > > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1826) > at > > org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233) > at > > org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297) > at > > org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.lambda$new$0(ServerImpl.java:2663) > at > > org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:7181) > at > > org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2700) > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) > at > > org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7119) > at > org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
