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 2021/02/24 08:52:00 UTC
[jira] [Assigned] (GEODE-8698) Remove TcrPoolEndPoint::registerDM
unnecessary DM lock
[ https://issues.apache.org/jira/browse/GEODE-8698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mario Salazar de Torres reassigned GEODE-8698:
----------------------------------------------
Assignee: Mario Salazar de Torres
> Remove TcrPoolEndPoint::registerDM unnecessary DM lock
> ------------------------------------------------------
>
> Key: GEODE-8698
> URL: https://issues.apache.org/jira/browse/GEODE-8698
> Project: Geode
> Issue Type: Bug
> 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
>
> Within TcrPoolEndPoint::registerDM, there is a lock for the DM connection queue mutex,
> which is not really necessary given that, as stated before, having a hard restriction on the connection number is not a must.
> Problem with this lock is that if any of the pool endpoints fails, connections are on hold while this endpoint is restored.
> One of the examples I've seen is that whenever a server goes down, and a pool with subscription enabled tries to re-open the subscription connection, all of the threads get locked due to this, even if they are not connecting to the server which is failing.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)