You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2015/11/23 18:42:11 UTC
[jira] [Updated] (TINKERPOP3-709) Consider Bounding Gremlin Pool
Queue Size
[ https://issues.apache.org/jira/browse/TINKERPOP3-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette updated TINKERPOP3-709:
----------------------------------------
Assignee: (was: stephen mallette)
> Consider Bounding Gremlin Pool Queue Size
> -----------------------------------------
>
> Key: TINKERPOP3-709
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-709
> Project: TinkerPop 3
> 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)