[
https://issues.apache.org/jira/browse/TINKERPOP-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318395#comment-17318395
]
Stephen Mallette commented on TINKERPOP-709:
--------------------------------------------
This issue will close with TINKERPOP-2245 - added {{gremlinPool}} bounds for
the new {{Channelizer}} for 3.5.0 that unifies the thread pools for sessionless
and in-session requests
> Consider Bounding Gremlin Pool Queue Size
> -----------------------------------------
>
> Key: TINKERPOP-709
> URL: https://issues.apache.org/jira/browse/TINKERPOP-709
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.0.2-incubating
> Reporter: Stephen Mallette
> Priority: Major
>
> Wonder if it's a good idea to make the queue size to the "gremlinPool"
> configurable and thus bounded.
> {code}
> final BlockingQueue<Runnable> queue = new ArrayBlockingQueue<>(queueSize);
> gremlinExecutorService = new ThreadPoolExecutor(n, n,
> 0L, TimeUnit.MILLISECONDS,
> queue);
> {code}
> If the queue exceeded {{queueSize}} it would throw:
> {{RejectedExecutionException}}. This approach would also provide another
> metric to capture/report: {{queue.size()}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
