[ https://issues.apache.org/jira/browse/TINKERPOP-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566602#comment-16566602 ]
ASF GitHub Bot commented on TINKERPOP-1774: ------------------------------------------- Github user spmallette commented on a diff in the pull request: https://github.com/apache/tinkerpop/pull/903#discussion_r207179625 --- Diff: docs/src/upgrade/release-3.4.x.asciidoc --- @@ -177,6 +177,17 @@ when dealing with that event. To make this easier, the event now raises with a ` link:https://issues.apache.org/jira/browse/TINKERPOP-1831[TINKERPOP-1831] +==== Gremlin.Net: Configurable Max and Min ConnectionPool Sizes + +Gremlin.Net's `ConnectionPool` now has a minimum and a maximum size. These sizes are configurable through added --- End diff -- Minor grammatical fix by adding the phrase "the newly" - "These sizes are configurable through the newly added `ConnectionPoolSettings`". > Gremlin .NET: Support min and max sizes in Connection pool > ---------------------------------------------------------- > > Key: TINKERPOP-1774 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1774 > Project: TinkerPop > Issue Type: Improvement > Components: dotnet > Affects Versions: 3.2.7 > Reporter: Jorge Bay > Assignee: Florian Hockmann > Priority: Minor > > Similar to the java connection pool, we should limit the maximum amount of > connections and start with a minimum number. > It would also a good opportunity to remove the synchronous acquisitions of > {{lock}} in the pool implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)