[
https://issues.apache.org/jira/browse/IGNITE-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809632#comment-16809632
]
Alexey Goncharuk commented on IGNITE-11614:
-------------------------------------------
[~ascherbakov] is there any difference for an end-user whether the transaction
is rolled back by timeout or not? If there is a race, it means that both cases
happen simultaneously, so any of them may be chosen. At the same time, there is
a CAS in {{rollbackNearTxLocalAsync}} for finish future, so only one of them
will proceed.
> Transaction with timeout on cache hangs after cache store failure
> -----------------------------------------------------------------
>
> Key: IGNITE-11614
> URL: https://issues.apache.org/jira/browse/IGNITE-11614
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Anton Kurbanov
> Assignee: Alexey Goncharuk
> Priority: Critical
> Fix For: 2.8
>
> Attachments: CacheStoreTxPutAllMultiNodeTest.java
>
>
> If CacheStore fails before/during transaction commit, transaction with set
> timeout remains active.
> Setting cfg.setTransactionConfiguration(new
> TransactionConfiguration().setTxTimeoutOnPartitionMapExchange(5000)); fixes
> the issue in test.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
