I am evaluating my cluster performance after migrating to 5.2. Everything looks fine from indexing to search to updates in terms of thread pools. whenever I run the thread_pool cat API all the queues are empty or have a couple of requests being processed except for the warmer threads. Same can be said about viewing hot threads as it shows warmers as the majority of threads running at any given time; almost 99% of the hot threads are warmers.
I want to know if there is a way to throttle the warmer threads, delay the threads from constantly running or if there is a way to disable warmers temporarely as I am experiencing some high CPU usage compared to what I had in ES 1.7 before upgradiing and I just want to know if this is caused by the warmer threads or from one of my requests.