[
https://issues.apache.org/jira/browse/IGNITE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729458#comment-16729458
]
Vladimir Ozerov commented on IGNITE-10434:
------------------------------------------
[~gvvinblade], regarding p.1 - but where is this "full set of rows" is stored?
From what I know, we get iterator, then walk over it and lock entries one by
one. So when lazy mode is enabled, it will trigger SQL executions.
> MVCC: Transaction asynchronous rollback bug.
> --------------------------------------------
>
> Key: IGNITE-10434
> URL: https://issues.apache.org/jira/browse/IGNITE-10434
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Roman Kondakov
> Assignee: Igor Seliverstov
> Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> There is some bug in mvcc tx asynchronous rollback flow. Sometimes
> transaction is not rolled back completely: Remote transactions remain alive
> while Near and Dht transactions are terminated locally and on MVCC
> coordinator.
> Reproducer: {{MvccTxRollbackAsyncTest#testMixedAsyncRollbackTypes}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
