tree 714fa802d110d1df685cb693a4c8daffc0d983d1
parent 6a60434984ab131e5910442fb7c29245a1e442e1
author Kirk Lund <klund@apache.org> 1634602592 -0700
committer GitHub <noreply@github.com> 1634602592 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhbg5gCRBK7hj4Ov3rIwAAppoIAKiHCFa1bPU4uOkspY/1mcqB
 NBGh8YUFrV4esPn+QWPn5H4EiNir4slVrXEnMHATL+RkuODkYQWPf5X+9Dr7jDsb
 0+aPH6AVDQDCZBiQwpo62wPMRG387s+XvI+jEibkAg2tveLdrBdIASY4uXw8ZfdV
 0ByJrHy1eibBO4QhoBRoHJTm626WrodpsLovtjSVJHmzisORYkE9W8zVTbXO1bjm
 Go/jXrzTqEyUIcDRbjk1CW4gvdjC+Q6QcDl/MrmQsajuEr6D60767hlG3VqNpJVO
 Nzz3RdJyrNnCu7XkOPN+CeRiYgaWh9t40nx2+kg0dbvq7PQofGGSfu/3we+VKIk=
 =YaY+
 -----END PGP SIGNATURE-----
 

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.