Apache Ignite is how to ensure the data's consistency between multiple server?

classic Classic list List threaded Threaded
8 messages Options
上帝已死 上帝已死
Reply | Threaded
Open this post in threaded view
|

Apache Ignite is how to ensure the data's consistency between multiple server?

Apache Ignite is how to ensure the data's consistency between multiple server?Especially, in the case of high concurrency.
上帝已死 上帝已死
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite is how to ensure the data's consistency between multiple server?

How does Apache Ignite ensure the data between multiple server is consistency in anytime?
christos christos
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite is how to ensure the data's consistency between multiple server?

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, 上帝已死 <[hidden email]> 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
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

christos christos
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite is how to ensure the data's consistency between multiple server?

Have a look at this:

On 1 Mar 2016, at 10:37, Christos Erotocritou <[hidden email]> 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, 上帝已死 <[hidden email]> 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
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


上帝已死 上帝已死
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite is how to ensure the data's consistency between multiple server?

In reply to this post by 上帝已死
PS: Cache mode is Replicated.
dsetrakyan dsetrakyan
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite is how to ensure the data's consistency between multiple server?


On Tue, Mar 1, 2016 at 2:34 AM, 上帝已死 <[hidden email]> wrote:
PS: Cache mode is Replicated.

 
Same documentation that Christos suggested applies to both, partitioned and replicated caches. Also, please take a look at the transaction documentation here:


上帝已死 上帝已死
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite is how to ensure the data's consistency between multiple server?

applies to both? Sorry, I don't understand your mean.
yakov yakov
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite is how to ensure the data's consistency between multiple server?

"Both" means REPLICATED and PARTITIONED.

You can also think of replicated cache as of partitioned configured with unlimited number of backups.

--Yakov

2016-03-02 10:48 GMT+03:00 上帝已死 <[hidden email]>:
applies to both? Sorry, I don't understand your mean.



--
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-tp3288p3333.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.