ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@gridgain.com>
Subject Re: 2PC & local storage
Date Mon, 01 Aug 2016 14:41:56 GMT
Hi Ionut,

In this scenario 2PC will work in a different way if to compare to a shared
DB case. A transaction coordinator won't commit data to a local store from
its side. This will be done on primary and backup nodes at commit phase. The
data will be committed to the local storage before and if this operation
succeeds a node will commit changes in memory as well.


ionut_s wrote
> Hi,
> There are articles (
> http://gridgain.blogspot.ro/2014/09/two-phase-commit-for-distributed-in.html
> <http://>  
>  and 
> http://gridgain.blogspot.ro/2014/09/two-phase-commit-for-in-memory-caches.html
> <http://>  
> ) explaining the design of 2PC in Ignite. One of the points mentioned in
> these articles is that data in Ignite is volatile therefore the 2PC is
> simpler. 
> My question is what happens when data is stored locally (@CaheLocalStore).
> Does the 2PC protocol changes in this case? 
> Thanks,
> Ionut

View this message in context: http://apache-ignite-users.70518.x6.nabble.com/2PC-local-storage-tp6367p6659.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message