Hello! I think I've just answered the same question for 2.8.1: https://lists.apache.org/thread.html/r102cf85775f7759e6772ceeed6d3a6843ea736b20647020fb8374833%40%3Cuser.ignite.apache.org%3E
I'm not sure why your node does not recognize itself as SEGMENTED. [15:04:29,711][SEVERE][tcp-client-disco-sock-writer-#2%ignite-instance-a5430afb-05b7-4492-9825-460966133ad1%-#47%ignite-instance-a5430afb-05b7-4492-9825-460966133ad1%][TcpDiscoverySpi] Failed to send message: null java.io.IOException: Failed to get acknowledge for message: TcpDiscoveryClientMetricsUpdateMessage [super=TcpDiscoveryAbstractMessage [sndNodeId=null, id=0610eed9771-841c8962-775e-4109-bc74-2c003598a02d, verifierNodeId=null, topVer=0, pendingIdx=0, failedNodes=null, isClient=true]] at org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1471) at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:58) Maybe there's something in your network configuration which prevents relaying of "connection closed" packets from client to server? Can you collect thread dump from such failing client when it has already started to exhibit that behavior? Regards, -- Ilya Kasnacheev пн, 15 февр. 2021 г. в 11:00, Charlin S <charli...@hotelhub.com>: > Hi, > > i'm running an ASP.Net application with ignite 2.9.1 and seeing below > error details in ignite client log and my web site stopped working. I have > faced the same issue with ignite 2.8.1 and I have upgraded 2.9.1 just > before 1 day, since ignite 2.9.0 release notes saying below points: > 1. Fixed processing of failure detection timeout in TcpDiscoverySpi. If a > node fails to send a message or ping, now it drops the current connection > strictly within this timeout and begins establishing a new connection much > faster. > 2. Fixed processing of connection recovery timeout in TcpDiscoverySpi. If > a node loses connection, now it strictly obtains a new connection to the > ring of gets segmented within this timeout. > > It's back to normal after restarting the application pool. > Please any suggestions? to avoid such issues. > Log files attached here for your reference. > > Thanks & Regards, > Charlin > >
