[
https://issues.apache.org/jira/browse/IGNITE-27838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-27838:
---------------------------------------
Summary: Directly mapped transactions can leave unreleased lock on internal
rollback (was: Directly mapped transactions can leave unreleased lock on
internal rollbacks)
> Directly mapped transactions can leave unreleased lock on internal rollback
> ---------------------------------------------------------------------------
>
> Key: IGNITE-27838
> URL: https://issues.apache.org/jira/browse/IGNITE-27838
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexey Scherbakov
> Assignee: Alexey Scherbakov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
>
> Currently in case of mapping error a transaction is rolled back on
> coordinator (see postEnlist)
> But for client's directly mapped transactions full enlistment state is
> available on coordinator only before finish.
> This can cause stale locks to remain until timeout invalidates them.
> The fix is to propagate rollback request to a client.
> Also affects rolbacks from kill()
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
