[jira] [Created] (IGNITE-18815) C++ 3.0: Transaction should be rolled back synchronously on destruction

["Igor Sapego (Jira)" <ji...@apache.org>]

Igor Sapego created IGNITE-18815:
------------------------------------

             Summary: 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
             Fix For: 3.0.0-beta2


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.



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