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 Scherbakov (Jira)" <ji...@apache.org> on 2026/01/21 10:24:00 UTC

[jira] [Updated] (IGNITE-27617) Directly mapped client transactions are not properly cleaned up

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

Alexey Scherbakov updated IGNITE-27617:
---------------------------------------
    Description: 
I've found a scenario, in which direcly mapped transaction write intents are not properly cleaned up on finish.
This is a regression after IGNITE-26458 and related to incorrect cleanup logic in case no writes are mapped on coordinator.

  was:
I've found a scenario, in which direcly mapped transaction write intents are not properly cleaned up on commit.
This is a regression after IGNITE-26458 and related to incorrect cleanup logic in case no writes are mapped on coordinator.


> Directly mapped client transactions are not properly cleaned up
> ---------------------------------------------------------------
>
>                 Key: IGNITE-27617
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27617
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Scherbakov
>            Assignee: Alexey Scherbakov
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> I've found a scenario, in which direcly mapped transaction write intents are not properly cleaned up on finish.
> This is a regression after IGNITE-26458 and related to incorrect cleanup logic in case no writes are mapped on coordinator.



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