[IGNITE-18818] .NET: Thin 3.0: Improve locking granularity in ClientFailoverSocket

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-beta1
• Fix Version/s: 3.0.0-beta2
• Component/s: platforms, thin client
• Labels: .NET ignite-3

Language

C#

• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Reviewer: Igor Sapego
• Created: 16/Feb/23 09:48
• Updated: 16/Feb/23 14:42
• Resolved: 16/Feb/23 14:42

Description

ClientFailoverSocket takes _socketLock for the entire GetSocketAsync method, which is called for every request. This can cause unnecessary contention.

We don't need to take the lock when using one of the existing, healthy connections. Only when a reconnect is required.

Issue Links

• blocks: IGNITE-18808 .NET: Thin 3.0: Reconnect secondary endpoints in background
• links to: GitHub Pull Request #1685
• links to: IGNITE-18818 .NET: Improve locking granularity in ClientFailoverSocket by ptupitsyn · Pull Request #1685 · apache/ignite-3