[
https://issues.apache.org/jira/browse/IGNITE-21540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-21540:
---------------------------------------
Description:
h3. Motivation
Deadlock prevention can throw a lock exception, but it depends on the
situation. After several retries, the exception might pass because another
transaction has already released its locks.
h3. Implementation notes
We need to consider all kinds of implicit operations that lead to the creation
of RW transactions.
h3. Definition of done
Implicit operations never throw the lock exception.
was:
h3. Motivation
Implicit operations create a transaction under the hood, and the transaction
may be in conflict with another one. This type of transaction can be
automatically retried because it does not contain user logic.
h3. Implementation notes
We need to consider all kinds of implicit operations that lead to the creation
of RW transactions.
h3. Definition of done
Implicit operations never throw the lock exception.
> Handle lock exception for transaction operations
> ------------------------------------------------
>
> Key: IGNITE-21540
> URL: https://issues.apache.org/jira/browse/IGNITE-21540
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> Deadlock prevention can throw a lock exception, but it depends on the
> situation. After several retries, the exception might pass because another
> transaction has already released its locks.
> h3. Implementation notes
> We need to consider all kinds of implicit operations that lead to the
> creation of RW transactions.
> h3. Definition of done
> Implicit operations never throw the lock exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
