[jira] [Commented] (TINKERPOP-2550) Deadlock on Client initialization

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

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

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

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


   https://issues.apache.org/jira/browse/TINKERPOP-2550
   
   This change fixes a potential deadlock issue on `Client` initialization and may have some impact on https://issues.apache.org/jira/browse/TINKERPOP-2504 as well. I won't re-document the points of this change here as I went to considerable lengths to explain it in code comments. Please see the rationale for the changes there.
   
   VOTE +1


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Deadlock on Client initialization
> ---------------------------------
>
>                 Key: TINKERPOP-2550
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2550
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: driver
>    Affects Versions: 3.4.10
>            Reporter: Stephen Mallette
>            Assignee: Stephen Mallette
>            Priority: Blocker
>
> Observed from TINKERPOP-2504 but also identified elsewhere. When the {{workerPoolSize}} is insufficiently sized it can lead to deadlock because the {{Host}} is blocking for its {{ConnectionPool}} to initialize and there will be no threads left to service the latter which keeps the former stuck.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)