SERVER-134361ClosedFixed

Add pool of threads to be used in parallel queries

There is already a ThreadPool class, but it support only the scheduling of Future objects without a few features that Query Parallelism would rely on: # Renameable (so that logs triggered by a parallel stream for the thread bound to conn56 are printed as conn56-1, conn56-2, etc) # Server parameter to control maximum number (given the 127 tickets granted to Query by the WT engine, default size would be 64) # Single acquire() API that returns N threads in one shot, we don't want to schedule

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix
9.1.0-rc0
Components
Server components related to this issue

No components specified.

Labels
Tags and classification
PQm1