Hi Ilya, The node communication issue is because one of the node is being restarted - and not due to network failure . The original issue is as below : Our setup :Servers - 3 node clusterReader clients : wait for an update on an entry of a cache ( around 20 ofthem )Writer Client : 1If one of the reader client restarts while the writer is writing into theentry of the cache , the server attempts to send the update to the failedclient's local listener . It keeps attempting to communicate with the failedclient ( client's continous query local listener ? ) till it timesout as perconnTimeoutStrategy=ExponentialBackoffTimeoutStrategy . ( Please find thesnippet of the exception below. The complete log is attached as anattachment ) This delays the completion of the transaction that was startedby the writer client.Is there any way the writer client could complete the transaction withoutgetting impacted by the reader client restarts ?regards,Veena.
-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
