if client and primary node all crashed, in this case, does ignite also ensure
data consistency? or only rely on "client put" next time?

there are my understands (1 primary and 2 backup):
in atomic mode, data consistency rely on client put, can not achieve "strong
consistent", ignite can not replace zookeeper;
in transaction mode, data consistency rely on 2pc protocol, can achieve
"strong consistent", ignite can replace zookeeper.

is this understanding correct?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/data-consistency-in-atomic-mode-tp11719p11730.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Reply via email to