[
https://issues.apache.org/jira/browse/IGNITE-27947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-27947:
---------------------------------------
Description:
Currently the client implicitly starts an explicit transaction on a first
enlist request.
This makes impossible to rollback the corrposponding transaction if it stuck on
first request (waiting for a lock for example), because no transaction handle
exists yet.
See
testRollbackDoesNotBlockOnLockConflictDuringFirstRequest for a reproducer.
was:
Currently the client carries a transaction start on a first request.
This makes impossible to rollback the corrposponding transaction if it stuck on
first request (waiting for a lock for example), because no transaction handle
exists yet.
See
testRollbackDoesNotBlockOnLockConflictDuringFirstRequest for a reproducer.
> Impossible to rollback client first transaction request
> -------------------------------------------------------
>
> Key: IGNITE-27947
> URL: https://issues.apache.org/jira/browse/IGNITE-27947
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexey Scherbakov
> Priority: Major
> Labels: ignite-3
>
> Currently the client implicitly starts an explicit transaction on a first
> enlist request.
> This makes impossible to rollback the corrposponding transaction if it stuck
> on first request (waiting for a lock for example), because no transaction
> handle exists yet.
> See
> testRollbackDoesNotBlockOnLockConflictDuringFirstRequest for a reproducer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
