[
https://issues.apache.org/jira/browse/IGNITE-18052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-18052:
---------------------------------------
Description:
*Motivation:*
In some case, required to release a specific lock before to release all locks
for the key in transaction. This temporary lock is also called a short term
lock.
The issue is the implementation of HeapLockManager is release all locks for
specific key just worth to invoke a release method one time.
There are no counters to conduct how many times lock was taken.
*Definition of done:*
Short term locks are acquired and released as described above.
*Implementation notes:*
A new method should be added:
{code:java}
// Some comments here
void release(UUID txId, LockKey lockKey, LockMode lockMode);
{code}
was:
*Motivation:*
According to the transaction protocol IEP [1] insert operation in RW
transactions for sortex index looks as follows:
_Unique index:_
// insert
IX_short(nextKey) // released after the insertion
X_commit(currentKey) // acquired before releasing IX_short
_Non-unique index:_
// insert
IX_short(nextKey)
X_commit(currentKey) if nextKey previously locked in S, X or SIX mode
IX_commit(currentKey) otherwise
This is necessary to avoid races between insert and scan operations. However,
it's not yet implemented.
*Definition of done:*
Short term locks are acquired and released as described above.
*Implementation notes:*
For the code related to locks for indexes, see
{{org.apache.ignite.internal.table.distributed.IndexLocker}}. We are interested
in {{SortedIndexLocker}} implementation, method {{locksForInsert}}. Actually,
there is some draft, but it is commented.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-91%3A+Transaction+protocol
> Introduce short term locks for sorted indexes operations
> --------------------------------------------------------
>
> Key: IGNITE-18052
> URL: https://issues.apache.org/jira/browse/IGNITE-18052
> Project: Ignite
> Issue Type: Improvement
> Reporter: Denis Chudov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *Motivation:*
> In some case, required to release a specific lock before to release all locks
> for the key in transaction. This temporary lock is also called a short term
> lock.
> The issue is the implementation of HeapLockManager is release all locks for
> specific key just worth to invoke a release method one time.
> There are no counters to conduct how many times lock was taken.
> *Definition of done:*
> Short term locks are acquired and released as described above.
> *Implementation notes:*
> A new method should be added:
> {code:java}
> // Some comments here
> void release(UUID txId, LockKey lockKey, LockMode lockMode);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
