Guys, let me step in and explain how it works with a 3rd party database like an RDBMS.
1. Write-through mode (all the changes are persisted right away). Transaction coordinator commits a transaction at the RDBMS level first and only *then* commits it at the cluster level. This is actually what that blog is about. So, the transaction coordinator (your application) maintains a direct connection to the database. If the transaction failed at the database level it won’t be committed on the cluster side at all. 2. Write-behind mode (the changes are persisted asynchronously). Transaction coordinator commits a transaction at the cluster level and primary nodes will commit the changes asynchronously depending on the workload and settings of the write-behind store impl that writes to your database. Hope this helps. — Denis > On Jan 11, 2018, at 3:35 AM, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com> > wrote: > > Local store means store, that resides only on one node. No other nodes see it. > > If you don't have local stores in cluster(only distributed ones), then it > will be the only db connection within transaction opened. > But If you have local stores, then nodes could open their own connections to > local stores(i.e. in replicated cache nodes could open connections to local > stores, if any). > > Only local stores could be filled with data from backup nodes, therefore new > connection must be opened(cannot reuse old one from primary node). > > > чт, 11 янв. 2018 г. в 13:48, Andrey Nestrogaev <a.nestrog...@flexsoft.com > <mailto:a.nestrog...@flexsoft.com>>: > Hi Aleksey, thanks for info, > > "/Actually, data could be persisted not on tx initiating node, but on > primary(I.e. we have partitioned cache and local cache)/" > Ok, but no matter where the data is persisted, there will always be only 1 > database connection within the transaction, no matter how many nodes are > involved in the transaction. > Right? > > "/Additionally, data would be persisted on backup node if you enable the > corresponding flag./" > Would be persisted on backup node with using the same database connection as > for primary node? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > <http://apache-ignite-users.70518.x6.nabble.com/> > > > -- > Best Regards, > > Kuznetsov Aleksey >
