Have a look at this: https://apacheignite.readme.io/docs/primary-and-backup-copies <https://apacheignite.readme.io/docs/primary-and-backup-copies>
> On 1 Mar 2016, at 10:37, Christos Erotocritou <[email protected]> wrote: > > If you use full sync mode for backups, then the client node will wait for > write or commit to complete on all participating remote nodes (primary and > backup). This is the most restrictive configuration but will guarantee data > consistency. > > In addition if you use transactions for any grid operations this will also > guarantee that data changes will only be committed only if the whole > transaction is successful i.e. if an object with an acquired optimistic lock > changes then transaction will fail and any changes will be rolled back. > > >> On 1 Mar 2016, at 10:19, 上帝已死 <[email protected] <mailto:[email protected]>> >> wrote: >> >> How does Apache Ignite ensure the data between multiple server is consistency >> in anytime? >> >> >> >> -- >> View this message in context: >> http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-is-how-to-ensure-the-data-s-consistency-between-multiple-server-tp3288p3291.html >> >> <http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-is-how-to-ensure-the-data-s-consistency-between-multiple-server-tp3288p3291.html> >> Sent from the Apache Ignite Users mailing list archive at Nabble.com >> <http://nabble.com/>. >
