[jira] [Closed] (TINKERPOP-3181) Allow Client initialization to succeed even if minPoolSize is not met

["Stephen Mallette (Jira)" <ji...@apache.org>]

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

Stephen Mallette closed TINKERPOP-3181.
---------------------------------------
    Fix Version/s: 4.0.0
                   3.8.0
                   3.7.5
       Resolution: Fixed

> Allow Client initialization to succeed even if minPoolSize is not met
> ---------------------------------------------------------------------
>
>                 Key: TINKERPOP-3181
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-3181
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: driver
>    Affects Versions: 3.7.4
>            Reporter: Stephen Mallette
>            Assignee: Stephen Mallette
>            Priority: Major
>             Fix For: 4.0.0, 3.8.0, 3.7.5
>
>
> If the {{ConnectionPool}} encounters a failure of just 1 {{Connection}} given the {{minPoolSize}}  it will close the pool and leave the {{Client}} in a state of host unavailability. That seems heavy handed, particularly if most of the {{minPoolSize}} is filled. Change it so that the pool is allowed to succeed in initialization on error so long as it is not empty. Normal driver recovery can then kick in.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)