[
https://issues.apache.org/jira/browse/IGNITE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16643132#comment-16643132
]
ASF GitHub Bot commented on IGNITE-9558:
----------------------------------------
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4933
IGNITE-9558
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9558
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4933.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 #4933
----
commit 16b231dfe56042d612f32e8162b59d374c55c037
Author: Ilya Lantukh <ilantukh@...>
Date: 2018-10-08T11:31:45Z
IGNITE-9558 : Changed remap check.
commit 031919f172613a458eae520e14d03672acaa4d5a
Author: Ilya Lantukh <ilantukh@...>
Date: 2018-10-08T12:17:08Z
IGNITE-9558 : Aff ready future.
----
> Avoid changing AffinityTopologyVersion on client connect when possible
> ----------------------------------------------------------------------
>
> Key: IGNITE-9558
> URL: https://issues.apache.org/jira/browse/IGNITE-9558
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: Alexey Goncharuk
> Assignee: Ilya Lantukh
> Priority: Major
>
> Currently a client join event changes discovery topology version which, in
> turn, changes AffinityTopologyVersion.
> When a client maps transaction on new AffinityTopologyVersion, corresponding
> message is not processed on remote node until remote node receives the
> corresponding discovery event. If discovery event delivery is delayed for
> some reason, this will result in transaction stalls on client joins.
> Since the client node does not change partition affinity, we can safely map
> transactions on the previous topology version and do not change the affinity
> topology version at all.
> Some cases need special care and probably do not qualify for this
> optimization, such as when client has near cache or client hosts partition
> for REPLICATED cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
