[
https://issues.apache.org/jira/browse/IGNITE-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520123#comment-16520123
]
Alexei Scherbakov commented on IGNITE-8820:
-------------------------------------------
[~ivandasch],
1. You've removed important message "Consider changing
TransactionConfiguration.txTimeoutOnPartitionMapSynchronization to non default
value to avoid this message". Please return it back with valid property
reference: txTimeoutOnPartitionMapExchange
2. You should ensure what tx rollback attempt is performed only once. I suggest
removing duplicated code from exchange future (because waitPartitionRelease is
called twice) and keep it only in exchange manager.
> Add ability to accept changing txTimeoutOnPartitionMapExchange while waiting
> for pending transactions.
> ------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-8820
> URL: https://issues.apache.org/jira/browse/IGNITE-8820
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.5
> Reporter: Ivan Daschinskiy
> Assignee: Ivan Daschinskiy
> Priority: Minor
> Fix For: 2.6
>
>
> Currently, if ExchangeFuture waits whith old value of
> txTimeoutOnPartitionMapExchange, new value is not accepted until next
> exchange starts. Sometimes it's very usefull (while timeout is too long and
> must be shorter applied immediatelly)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
