ExecutorUtils.createSingleThreadSchedulingDeamonPool ends up creating number of threads equal to the desired queue amount

[ryanrupp]

See the method here which indicates it should be a single thread and has an input parameter for queue size. However, it ends up calling new ScheduledThreadPoolExecutor(corePoolSize, threadFactory) passing the queueCapacity parameter to the corePoolSize. This is used by Elasticsearch reporting code which I believe is trying to batch together requests so should only need 1 thread really (short of getting blocked maybe?).

[ryanrupp]

See the above threads for instance, queueCapacity is passed as 10 but we end up with 10 threads then.