[
https://issues.apache.org/jira/browse/IGNITE-27947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072587#comment-18072587
]
Tiago Marques Godinho commented on IGNITE-27947:
------------------------------------------------
Since https://issues.apache.org/jira/browse/IGNITE-24963 it's already around
the corner, we decided to postpone this merge until then.
It will allow us to remove the disable condition from the test, since it will
be the default behaviour.
> Impossible to rollback client first transaction request
> -------------------------------------------------------
>
> Key: IGNITE-27947
> URL: https://issues.apache.org/jira/browse/IGNITE-27947
> Project: Ignite
> Issue Type: Bug
> Components: platforms ai3
> Affects Versions: 3.1
> Reporter: Alexey Scherbakov
> Assignee: Tiago Marques Godinho
> Priority: Major
> Labels: ignite-3
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> 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.
> Also need to get rid of future.join() in ClientLazyTransaction because it's
> uninterruptable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
