[jira] [Comment Edited] (TINKERPOP-2288) Get ConnectionPoolBusyException and then ServerUnavailableExceptions

["Maurice Bachor (Jira)" <ji...@apache.org>]

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

Maurice Bachor edited comment on TINKERPOP-2288 at 5/8/20, 8:42 PM:
--------------------------------------------------------------------

Ok, I have been running several tests and there is at least one conclusion. The client cannot be used as a singleton in conjunction with cosmos db. It keeps eating up the tcp connections over time (I am doing loads against cosmos db, so many thousand requests).

!image-2020-05-08-22-37-18-834.png|width=401,height=139!

And I get the socket exceptions on top while this is running. Here the number of tcp established of the azure service app plan is displayed. When it hits the barrier of connections of the app plan it totally fails of course.


was (Author: bachor):
Ok, I have been running several tests and there is at least one conclusion. The client cannot be used as a singleton in conjunction with cosmos db. It keeps eating up the tcp connections over time (I am doing loads against cosmos db, so many thousand requests).

!image-2020-05-08-22-37-18-834.png!

> Get ConnectionPoolBusyException and then ServerUnavailableExceptions
> --------------------------------------------------------------------
>
>                 Key: TINKERPOP-2288
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2288
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: dotnet
>    Affects Versions: 3.4.1
>         Environment: Gremlin.Net 3.4.1
> Microsoft.NetCore.App 2.2
> Azure Cosmos DB
>            Reporter: patrice huot
>            Priority: Critical
>         Attachments: Gremlin.Net.3.4.7-SNAPSHOT.nupkg, image-2020-05-08-22-37-18-834.png
>
>
> I am using .Net core Gremlin API  query Cosmos DB.
> From time to time we are getting an error saying that no connection is available and then the server become unavailable. When this is occurring we need to restart the server. It looks like the connections are not released properly and become unavailable forever.
> We have configured the pool size to 50 and the MaxInProcessPerConnection to 32 (Which I guess should be sufficient).
> To diagnose the issue, Is there a way to access diagnostic information on the connection pool in order to know how many connections are open and how many processes are running in each connection?
> I would like to be able to monitor the connections usage to see if they are about to be exhausted and to see if the number of used connections is always increasing or of the connection lease is release when the queries completes?
> As a work around, Is there a way we can access this information from the code so that I can catch those scenario and create logic that re-initiate the connection pool?
>  
>  



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