ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bingili <b...@illinois.edu>
Subject Ignite Transaction with Locks but not SERIALIZABLE user case.
Date Tue, 31 Oct 2017 05:39:01 GMT

I have some operations which does not care about the order, e.g., each
operation is to increase the key value by 1 or decrease by 1. 

So I need a lock to protect each key on read and write. Also I need to put
operations in transaction, since ignite will handle the commit and rollback. 

Put them together, I found that Pessimistic Transactions seems to work for
this user case, but SERIALIZABLE is too strict on this case. For my user
case, It is OK to interleave between transactions as long as read/write
protection on each overlapping key between concurrent transactions. I do not
need SERIALIZABLE since that will degrade my throughput.

May I know if there is a better way to handle this user case, please?
Hope my question is clear.


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

View raw message