Hello! It seems that your node had segmented (due to network glitch or long GC), and stumbled on the following bug: https://issues.apache.org/jira/browse/IGNITE-8751
You could upgrade to 2.7 to make it go away, but it won't solve the original node segmentation reason. Regards, -- Ilya Kasnacheev пт, 1 февр. 2019 г. в 04:48, aa...@tophold.com <aa...@tophold.com>: > Hi igniters, > > Under which circumstance we may receive the SYSTEM_WORKER_TERMINATION of > the Thread: tcp-disco-srvr*? > > We meet this several times, especially we leave the nodes running for > over 5 days or longer. the stack did not say too much: > > > > [ERROR] 2019-01-31 19:25:32.094 [tcp-disco-srvr#3%PortfolioEventIgnite%] [ig] > - Critical system error detected. Will be handled accordingly > > to configured handler [hnd=class o.a.i.failure.StopNodeOrHaltFailureHandler, > failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, > err=java.lang.IllegalStateException: Thread > tcp-disco-srvr-#3%PortfolioEventIgnite% is terminated unexpectedly.]] > > java.lang.IllegalStateException: Thread > tcp-disco-srvr-#3%PortfolioEventIgnite% is terminated unexpectedly. > > at > org.apache.ignite.spi.discovery.tcp.ServerImpl$TcpServer.body(ServerImpl.java:5686) > [ignite-core-2.6.0.jar!/:2.6.0] > > at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > [ignite-core-2.6.0.jar!/:2.6.0] > > > [ERROR] 2019-01-31 19:25:32.097 [tcp-disco-srvr#3%PortfolioEventIgnite%] [ig] > - JVM will be halted immediately due to the failure: > [failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, > err=java.lang.IllegalStateException: Thread > tcp-disco-srvr-#3%PortfolioEventIgnite% is terminated unexpectedly.]] > > The underling server environment seems health and underloaded. > > Thanks for your advice and time! > > Regards > Aaron > >
