[ https://issues.apache.org/jira/browse/TINKERPOP-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428760#comment-15428760 ]
stephen mallette commented on TINKERPOP-709: -------------------------------------------- After next bump of netty (4.0.40) might be able to make use of this: https://github.com/netty/netty/pull/5440 > 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 > > 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 (v6.3.4#6332)