You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2018/01/31 08:15:00 UTC

[jira] [Updated] (IGNITE-7486) Сache operation failed after transaction rolled back due to deadlock

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

Alexey Goncharuk updated IGNITE-7486:
-------------------------------------
    Fix Version/s: 2.5

> Сache operation failed after transaction rolled back due to deadlock
> --------------------------------------------------------------------
>
>                 Key: IGNITE-7486
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7486
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Kuznetsov
>            Priority: Major
>             Fix For: 2.5
>
>         Attachments: CacheOperationAfterTxDeadlockDetectedTest.java
>
>
> When you have your transaction rolled back due to detected deadlock, you are unabled to perform cache operations (in thread where tx was started and rolled back), because it leads to TransactionTimeoutException.
> The reason of such behavior is that tx thread map (txManager#threadMap) was not cleared from tx when roll back occured.
> In GridNearTxLocal#onTimeout you can find comment on that :
> // Note: if rollback asynchronously on timeout should not clear thread map
>                     // since thread started tx still should be able to see this tx.
> Cache operation picks up tx from that map and throws exception.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)