[
https://issues.apache.org/jira/browse/IGNITE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16614791#comment-16614791
]
ASF GitHub Bot commented on IGNITE-9558:
----------------------------------------
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4761
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/4761.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 #4761
----
commit b1a17a82619b72c73453541ba2b85ac77a224050
Author: Ilya Lantukh <ilantukh@...>
Date: 2018-09-14T12:48:35Z
IGNITE-9558 : Assert for externalizable methods in ATV.
----
> 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)