[teiid-issues] [JBoss JIRA] (TEIID-5415) Simplify connection handling

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-5415.
-----------------------------------
    Fix Version/s: 11.1
                       (was: 11.x)
       Resolution: Done


Updated the docs to remove any post connection load balancing and added references to haproxy.

> Simplify connection handling
> ----------------------------
>
>                 Key: TEIID-5415
>                 URL: https://issues.jboss.org/browse/TEIID-5415
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: JDBC Driver
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 11.1
>
>
> With the removal of TEIID-5411 we can further simplify our notion of connection handling.  The current logic maintains a set of logins for known server instances under one logical connection.  When a connection is returned to an XA pool (or the client issues special sql) the logical connection will select a new instance using a cached login if possible.  
> The benefits of the current approach are:
> * works just from the hosts listed in the url
> * works with XA connection pooling or connection pooling in general with additional setup to provide simple load balancing
> The drawbacks are:
> * creates a set of logins which may mostly sit idle
> * is not load balancer aware - for example when just a load balanced end point is used.  And the load balancing is just random, not intelligent.
> * requires the client to keep a pool of physical connections
> A proposal would be to keep multiple url failover, but removal all of the logic related to maintaining multiple logins under a logical connection.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)