[IGNITE-18808] .NET: Thin 3.0: Reconnect secondary endpoints in background

• 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
• Ignite Flags: Docs Required, Release Notes Required

Language

C#

• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Reviewer: Igor Sapego
• Created: 15/Feb/23 11:29
• Updated: 20/Feb/23 14:15
• Resolved: 20/Feb/23 13:27

Description

On start, .NET thin client establishes 1 primary connection in foreground, and then connects to other known servers in the background. If the primary connection is lost, it is re-established automatically. However, when secondary connections are lost, they are not re-established, which means partition awareness and request balancing may not work as expected.

Use a timer to check and fix secondary connections periodically.

Issue Links

• fixes: IGNITE-18845 .NET: Thin 3.0: TestCustomColocationKey is flaky
• is blocked by: IGNITE-18818 .NET: Thin 3.0: Improve locking granularity in ClientFailoverSocket
• is cloned by: IGNITE-18809 Thin 3.0: Reconnect secondary endpoints in background
• is related to: IGNITE-18613 .NET: Thin 3.0: Balance requests across connections
• links to: GitHub Pull Request #1691
• links to: IGNITE-18808 .NET: Reconnect all endpoints periodically in background by ptupitsyn · Pull Request #1691 · apache/ignite-3