ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@apache.org>
Subject Re: 3rd Party Persistence and two phase commit
Date Thu, 11 Jan 2018 01:55:42 GMT
Covered here:
http://gridgain.blogspot.com/2014/09/two-phase-commit-for-in-memory-caches.html <http://gridgain.blogspot.com/2014/09/two-phase-commit-for-in-memory-caches.html>

—
Denis

> On Jan 10, 2018, at 8:27 AM, Denis Mekhanikov <dmekhanikov@gmail.com> wrote:
> 
> Hi Andrey!
> 
> Actually, commit to the 3rd party database will be performed from the node, that initiated
the transaction.
> So, there will be only one transaction on the backing database.
> Otherwise it is impossible to guarantee data consistency, as you noticed.
> 
> Denis
> 
> ср, 10 янв. 2018 г. в 18:58, Andrey Nestrogaev <a.nestrogaev@flexsoft.com <mailto:a.nestrogaev@flexsoft.com>>:
> Hi all!
> 
> We have a cache "Accounts".
> We use 3rd Party Persistence with Write-Through mode
> 
> In the cache there are two accounts.
> Account width id = 1 is located on node A and account with id = 2 is located
> on node B.
> In a single transaction we want to transfer the amount of $100 from account
> 1 to account 2.
> 
> How Ignite in the described case supports ACID transactions?
> What happens if the CacheStore on node A successfully executes the commit in
> the overrided method sessionEnd
> and when the sessionEnd method is executed on node B, an error occurs and
> the data is not commit in the database.
> 
> In this case, we get inconsistent data in the database, right?
> 
> Thanks!
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ <http://apache-ignite-users.70518.x6.nabble.com/>


Mime
View raw message