[
https://issues.apache.org/jira/browse/IGNITE-18815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689562#comment-17689562
]
Pavel Tupitsyn commented on IGNITE-18815:
-----------------------------------------
[~isapego] looks good to me.
> C++ 3.0: Transaction should be rolled back synchronously on destruction
> -----------------------------------------------------------------------
>
> Key: IGNITE-18815
> URL: https://issues.apache.org/jira/browse/IGNITE-18815
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 3.0.0-beta1
> Reporter: Igor Sapego
> Assignee: Igor Sapego
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, {{transaction_impl}} is rolled back asynchronously on destruction.
> This can result in locking conflicts looking like this:
> {noformat}
> Failed to acquire a lock due to a conflict
> [txId=000f7d63-d563-0000-0242-ac78000a0000, conflictingWaiter=WaiterImpl
> [txId=000f7d63-d55b-0000-0242-ac78000a0000, intendedLockMode=null,
> lockMode=X, ex=null, isDone=true]
> {noformat}
> Transaction should be rolled back synchronously on destruction.
> Test is to be un-muted when the issue is fixed:
> https://ci.ignite.apache.org/test/-3102268643379533778?currentProjectId=ApacheIgnite3xGradle_Test
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
