[
https://issues.apache.org/jira/browse/GEODE-9713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17448887#comment-17448887
]
ASF subversion and git services commented on GEODE-9713:
--------------------------------------------------------
Commit d6d9a9108150e2396ebe3ca91ee62c1e895cf040 in geode's branch
refs/heads/support/1.14 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d6d9a91 ]
GEODE-9713: Support thread count in ExecutorService rules (#7002)
Restores thread count support to ExecutorServiceRule, and adds it to
DistributedExecutorServiceRule.
PROBLEM
ExecutorService rules currently create a newCachedThreadPool which
creates new threads as needed.
Some usages would benefit from the option of specifying a threadCount
limit which would create a newFixedThreadPool that reuses a fixed
number of threads.
SOLUTION
Add optional threadCount creation parameter to both ExecutorServiceRule
and DistributedExecutorServiceRule.
Creating a ExecutorService rule without a threadCount will still create a
newCachedThreadPool. Using a threadCount will now create a
newFixedThreadPool.
(cherry picked from commit 636bea3fd14c634d2568ed49eba3b13f1797d1ff)
> DistributedExecutorServiceRule should have parameter to specify threadCount
> ---------------------------------------------------------------------------
>
> Key: GEODE-9713
> URL: https://issues.apache.org/jira/browse/GEODE-9713
> Project: Geode
> Issue Type: Wish
> Components: tests
> Reporter: Kirk Lund
> Assignee: Kirk Lund
> Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> DistributedExecutorServiceRule should have parameter to specify threadCount
> in addition to vmCount. ExecutorServiceRule has a parameter to specify
> threadCount so it's just a matter of propagating it to the super constructor.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
