Hi, This is possible in ATOMIC cache, because if the client doesn't receive the response from the failed node, it doesn't know if the value was removed or not. It will then get an exception and retry, but if the value was removed on the first iteration, false will be removed.
Can you try switching to TRANSACTIONAL cache [1]? It guarantees strict semantics and should fix your case. [1] https://apacheignite.readme.io/docs/transactions#atomicity-mode -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-atomic-conditional-remove-returns-error-when-node-leaves-cluster-tp4223p4245.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
