You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Shishkov (Jira)" <ji...@apache.org> on 2025/06/16 08:33:00 UTC

[jira] [Updated] (IGNITE-25681) Asynchronous rollback does not clean context for thread

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

Ilya Shishkov updated IGNITE-25681:
-----------------------------------
    Summary: Asynchronous rollback does not clean context for thread  (was: Can not perform cache operation in case of stale transaction)

> Asynchronous rollback does not clean context for thread
> -------------------------------------------------------
>
>                 Key: IGNITE-25681
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25681
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ilya Shishkov
>            Priority: Major
>              Labels: ise
>         Attachments: RollbackTest.patch
>
>
> If some delays (eg. GC-pause) happens during transaction initialization in the same way as described in IGNITE-25538, then you can not start any cache operation (i.e. implicit transaction) in a tread with such stale transaction.
> # Start server node.
> # Start tx with timeout (do not use 'try-with resources').
> # Inject sleep in IgniteTxManager#onCreated after isCompleted check with value slightly less, than tx timeout.
> # Wait for tx completion with timeout error.
> # Rollback transaction instead of closing it.
> # Transaction become stale now, but don't hold any locks.
> # You can not start any implicit transaction ever in this thread.
> # But, explicit transaction can be started.
> *Reproducer:*  [^RollbackTest.patch]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)