You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by zhouxy1123 <zh...@sina.com> on 2018/05/20 14:00:17 UTC

How dose ignite implement concurrent control in transaction?

hi , How dose ignite implement concurrent control in transaction?
Since Ignite support Read Repeat isolation,so in a transaction lock protocol
is tow phase with respect to exclusive lock and well-formed. Does Ignite
implement tow phase lock and granule lock to prevent phantom read.Besides
Dose Ignite support granular locks and intend lock?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: How dose ignite implement concurrent control in transaction?

Posted by Stanislav Lukyanov <st...@gmail.com>.
Hi,

To start with Ignite transactions, please use the following docs:
- Ignite transactions overview on readme.io: https://apacheignite.readme.io/docs/transactions
- Transaction class Javadoc: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/transactions/Transaction.html
- Deep-dive description of Ignite transactions’ architecture: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Key-Value+Transactions+Architecture

Please take a look at these links and if you still have questions after that please ask them here.

Thanks,
Stan 

From: zhouxy1123
Sent: 20 мая 2018 г. 17:00
To: user@ignite.apache.org
Subject: How dose ignite implement concurrent control in transaction?

hi , How dose ignite implement concurrent control in transaction?
Since Ignite support Read Repeat isolation,so in a transaction lock protocol
is tow phase with respect to exclusive lock and well-formed. Does Ignite
implement tow phase lock and granule lock to prevent phantom read.Besides
Dose Ignite support granular locks and intend lock?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/