[jira] [Updated] (GEODE-8553) Reduce ThinClientLocatorHelper lock time

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot updated GEODE-8553:
----------------------------------
    Labels: pull-request-available  (was: )

> Reduce ThinClientLocatorHelper lock time
> ----------------------------------------
>
>                 Key: GEODE-8553
>                 URL: https://issues.apache.org/jira/browse/GEODE-8553
>             Project: Geode
>          Issue Type: Improvement
>          Components: native client
>    Affects Versions: 1.12.0, 1.13.0
>            Reporter: Mario Salazar de Torres
>            Priority: Major
>              Labels: pull-request-available
>
> During my troublshootings, I've seen that locking m_locatorLock for the whole scope of the class function members might cause some inter-locks.
> Problem here and in many other places of the NC is that networking operations are performed while a mutex is locked. Therefore if *thread A* takes longer than expected in performing its network operation, it might block another one which does not requires any resource of the first *thread A*. Hence, the inter-lock.
> This improvement is the first one of a series regarding to lock scope reduction when it comes with code regarding networking in NC.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)