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/16 23:08:00 UTC

[jira] [Updated] (GEODE-6605) Simplify connection load conditioning

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

Jacob S. Barrett updated GEODE-6605:
------------------------------------
    Summary: Simplify connection load conditioning  (was: Simply connection load conditioning)

> Simplify connection load conditioning
> -------------------------------------
>
>                 Key: GEODE-6605
>                 URL: https://issues.apache.org/jira/browse/GEODE-6605
>             Project: Geode
>          Issue Type: Sub-task
>          Components: client/server
>            Reporter: Jacob S. Barrett
>            Priority: Major
>
> Currently load conditioning requires scanning the {{allConnections}} for N number of idle connections to specific servers. Each matching {{PooledConnection}} then has it's underlying {{Connection}} swapped out for one to a different server. This requires extra logic in the {{borrowConnection(forServer)}} method to check that the associated server hasn't changed between to matching and activation, if it has it must be placed back in the queue and the scan must be repeated. Removing the secondary pool will removed the need to swap out connections. Any matching idle connection from the {{availableConnections}} queue will just be destroyed. New connections will be created to the less loaded server either on demand or via pre-fill. No complicated logic for swapping connections is required and no recheck for chaining servers is required.



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