[
https://issues.apache.org/jira/browse/IGNITE-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515723#comment-16515723
]
ASF GitHub Bot commented on IGNITE-8820:
----------------------------------------
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/4217
IGNITE-8820: Add ability to read new value of txTimeoutOnPartitionMap…
…Exchange while exchange future runs.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ivandasch/ignite ignite-8820
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4217.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4217
----
commit 44dc068d5d9ffb4bbce8986a4195299ceb5b697c
Author: Ivan Daschinskiy <ivandasch@...>
Date: 2018-06-18T10:48:45Z
IGNITE-8820: Add ability to read new value of
txTimeoutOnPartitionMapExchange while exchange future runs.
----
> 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)
