You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Mario Salazar de Torres (Jira)" <ji...@apache.org> on 2020/09/29 18:58:00 UTC
[jira] [Created] (GEODE-8553) Reduce ThinClientLocatorHelper lock
time
Mario Salazar de Torres created GEODE-8553:
----------------------------------------------
Summary: 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.13.0, 1.12.0
Reporter: Mario Salazar de Torres
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)