[jira] [Created] (IGNITE-4285) Optimize locks for read-only keys in optimistic/serializable transactions

["Semen Boikov (JIRA)" <ji...@apache.org>]

Semen Boikov created IGNITE-4285:
------------------------------------

             Summary: Optimize locks for read-only keys in optimistic/serializable transactions
                 Key: IGNITE-4285
                 URL: https://issues.apache.org/jira/browse/IGNITE-4285
             Project: Ignite
          Issue Type: Task
          Components: cache
            Reporter: Semen Boikov
            Assignee: Semen Boikov
             Fix For: 2,0


Now when optimistic transaction acquires lock for key which is not modified by any other tx, then TransactionOptimisticException is still possible if read lock is already held by some other tx with higher tx version. 
Following optimziation is possible to avoid TransactionOptimisticException for mostly read keys: when try to add lock for 'read' key, and in locks queue there are only others 'read' locks, then lock can be acquired immediately without tx version check.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)