Hi Andrey, It turns out that we had increases our failureDetectionTimeout wayyy too much. After setting it to something more sensible, the issue stopped.
Thanks for the info, Rami -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Performance-issue-with-Replicated-Cache-among-7-nodes-tp12848p12880.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
