# Threadpool.index.queue\_size overflow **URL:** \ **Category:** Elasticsearch\ **Created:** [May 3, 2018, 8:24am UTC](https://discuss.elastic.co/t/threadpool-index-queue-size-overflow/130398 "2018-05-03T08:24:02Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![anoopvalluthadam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anoopvalluthadam/32/30286_2.png) [@anoopvalluthadam](https://discuss.elastic.co/u/anoopvalluthadam)\ **Post date:** [May 3, 2018, 8:24am UTC](https://discuss.elastic.co/t/threadpool-index-queue-size-overflow/130398/1 "2018-05-03T08:24:02Z")
Node configuration : 61.0 GiB 8 vCPUs and 8 nodes 3 master nodes and 5 data nodes ``` thread_pool.search.queue_size: 1000 ``` we have almost 300+ indices and 1 Percolator index. Per day indexing is 400K and this same 400K will be searching in percolator as well. So the CPU usage of 3 data nodes are always 92% how can we scale the setup for this much data ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 31, 2018, 8:24am UTC](https://discuss.elastic.co/t/threadpool-index-queue-size-overflow/130398/2 "2018-05-31T08:24:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.