[ 
https://issues.apache.org/jira/browse/GEODE-8553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17207583#comment-17207583
 ] 

ASF GitHub Bot commented on GEODE-8553:
---------------------------------------

lgtm-com[bot] commented on pull request #660:
URL: https://github.com/apache/geode-native/pull/660#issuecomment-703275195


   This pull request **introduces 2 alerts** when merging 
66c5679134de157db62c966be8ab3960b1973782 into 
2e64e74e3b29c9813776c80b34b84606ec7b8274 - [view on 
LGTM.com](https://lgtm.com/projects/g/apache/geode-native/rev/pr-09f33402e6c86fb562c26a7c9e1f1d1cf418fe6a)
   
   **new alerts:**
   
   * 2 for Wrong type of arguments to formatting function


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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
>            Assignee: 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)

Reply via email to