You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2024/03/22 10:26:00 UTC

[jira] [Updated] (IGNITE-21540) Handle lock exception for transaction operations

     [ https://issues.apache.org/jira/browse/IGNITE-21540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Lapin updated IGNITE-21540:
-------------------------------------
    Reviewer: Denis Chudov

> 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
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> 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)