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 cluster Reader clients : wait for an update on an entry of a cache ( around 20 of them ) Writer Client : 1 If one of the reader client restarts while the writer is writing into the entry of the cache , the server attempts to send the update to the failed client's local listener . It keeps attempting to communicate with the failed client ( client's continous query local listener ? ) till it timesout as per connTimeoutStrategy=ExponentialBackoffTimeoutStrategy . ( Please find the snippet of the exception below. The complete log is attached as an attachment ) This delays the completion of the transaction that was started by the writer client. Is there any way the writer client could complete the transaction without getting impacted by the reader client restarts ? regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
