You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jacob S. Barrett (JIRA)" <ji...@apache.org> on 2019/04/29 21:47:00 UTC

[jira] [Assigned] (GEODE-6604) Simplify connection lifetime expiration / load conditioning.

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

Jacob S. Barrett reassigned GEODE-6604:
---------------------------------------

    Assignee: Jacob S. Barrett

> Simplify connection lifetime expiration / load conditioning.
> ------------------------------------------------------------
>
>                 Key: GEODE-6604
>                 URL: https://issues.apache.org/jira/browse/GEODE-6604
>             Project: Geode
>          Issue Type: Sub-task
>          Components: client/server
>            Reporter: Jacob S. Barrett
>            Assignee: Jacob S. Barrett
>            Priority: Major
>
> Connection lifetime expiration currently requires scanning the {{allConnections}} set with exclusive lock looking for connections that are over the lifetime limit. If the connection needs to be expired then the {{PooledConnection}} as its {{Connection}} swapped out for a new one to the same server. If we remove the secondary pool then expired connections could simply be removed from the {{availableConnections}} and {{allConnections}} and destroyed. A new connection would be created either on demand of from pre-fill. No complicated logic is required to support swapping out the underlying {{Connection}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)