[ 
https://issues.apache.org/jira/browse/IGNITE-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-18818:
------------------------------------
    Ignite Flags:   (was: Docs Required,Release Notes Required)

> .NET: Thin 3.0: Improve locking granularity in ClientFailoverSocket
> -------------------------------------------------------------------
>
>                 Key: IGNITE-18818
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18818
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: .NET, ignite-3
>             Fix For: 3.0.0-beta2
>
>
> *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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to