[IGNITE-9558] Avoid changing AffinityTopologyVersion on client connect when possible

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.8
• Assignee: Ilya Lantukh
• Reporter: Alexey Goncharuk
• Created: 12/Sep/18 12:29
• Updated: 25/Mar/19 12:23
• Resolved: 19/Nov/18 12:17

Description

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.

Issue Links

• causes: IGNITE-11625 AffinityTopologyVersion should be changed on client connect when this client node has new statically configured cache(s).
• links to: GitHub Pull Request #4933