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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TINKERPOP-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014184#comment-18014184 ] 

ASF GitHub Bot commented on TINKERPOP-3181:
-------------------------------------------

spmallette opened a new pull request, #3187:
URL: https://github.com/apache/tinkerpop/pull/3187

   https://issues.apache.org/jira/browse/TINKERPOP-3181
   
   If the `ConnectionPool` creates at least one good connection on initialization, allow the `Client` to have an available `Host` even if it's less than the `minPoolSize`. Allow normal recovery options to attempt reconnects and fall into unavailability the standard ways.
   
   VOTE +1




> 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
>
> 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)