# How to set Thread Pool settings for all data nodes in 7.14 Elastic cloud **URL:** \ **Category:** Elasticsearch\ **Created:** [September 17, 2021, 10:21am UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473 "2021-09-17T10:21:18Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![rohitnagarro](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@rohitnagarro](https://discuss.elastic.co/u/rohitnagarro)\ **Post date:** [September 17, 2021, 10:21am UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473/1 "2021-09-17T10:21:18Z")
Hi, We have 200K video assets on Elastic cloud, consuming 500mb of space on single node. Configuration wise we have 32 GB RAM Elasticsearch in 3 Zone Dedicated Master with 1GB RAM | 8 vCPU | 3 Zone Coordinating node with 1GB RAM | 4VCPU | 3 Zone Kibana node 1GB RAM | 8 vCPU | 2 Zone Enterprise Search nodes 8 GB RAM | Up to 8 vCPU | 2 Zone We are targeting our application with load of 13 k request in 1 min for response time 5Oms per request. However our request are getting rejected/failed from elastic data node and getting response time min of 1ms max 25 sec. ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/b/db3aeeeea3f26a5cbec6233de7279323db8114f5.png) My questions are: Is this configuration is sufficient for load we are targeting? Can we set the thread pool size of each node in Elastic cloud? ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/e/7ef7487a0169486ea471dd74b31a5c98b4782e02.png) ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [September 19, 2021, 4:25pm UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473/2 "2021-09-19T16:25:02Z")
Hi @rohitnagarro Since you are using Elastic Cloud, you have support perhaps open a support ticket through the Elastic Cloud Console would be a good suggestion. Also is that instance 000000032 the coordinating node? If so 1GB is pretty small perhaps scale it up to 2GB x 3 Zones . All searches and ingests will pass through those coordinating nodes. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 19, 2021, 8:44pm UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473/3 "2021-09-19T20:44:25Z")
You state that the data set is 500MB in size but the cluster hold over 66GB of data. What is the size of the index/indices you are querying? How many primary and replica shards does it have? ---
**Author:** ![rohitnagarro](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@rohitnagarro](https://discuss.elastic.co/u/rohitnagarro)\ **Post date:** [September 20, 2021, 4:49am UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473/4 "2021-09-20T04:49:06Z")
Hi @stephenb, Thanks for your reply , I tried the support and however as per them "our current subscription level offers our world-class break/fix support, including general guidance and best practices. Although this question appears to be of a consultative nature outside of your subscription’s scope." Instance 000000032 is the "data node", will try with 2 GBx 3 Zones. ---
**Author:** ![rohitnagarro](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@rohitnagarro](https://discuss.elastic.co/u/rohitnagarro)\ **Post date:** [September 20, 2021, 5:37am UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473/5 "2021-09-20T05:37:23Z")
Hi @Christian_Dahlqvist , I mean the index we are searching on is ~500Mb in size and growing. there are other indices(total 126, 13 created by us, rest are related to actastic and other elastic internal) also and no search is happing on them when I am testing. Index under test is the one whose size is ~500MB rest indies created by us are of few KBs are has 2 primary and 1 replica. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 20, 2021, 6:33am UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473/6 "2021-09-20T06:33:02Z")
How many primary shards does this index have? ---
**Author:** ![rohitnagarro](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@rohitnagarro](https://discuss.elastic.co/u/rohitnagarro)\ **Post date:** [September 20, 2021, 6:44am UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473/7 "2021-09-20T06:44:33Z")
> [@rohitnagarro](#): > > dex under test is the one whose size is ~500MB rest indies created by us are of few KBs are has 2 primary and 1 replica. 2 primary shards ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 20, 2021, 6:58am UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473/8 "2021-09-20T06:58:42Z")
That is a small amount of data so I would recommend reindexing that into an index with a single primary shard. This should improve your handling of concurrent queries, especially if you have enough operating system page cache so the full index can be cached. ---
**Author:** ![rohitnagarro](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@rohitnagarro](https://discuss.elastic.co/u/rohitnagarro)\ **Post date:** [September 21, 2021, 10:38am UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473/10 "2021-09-21T10:38:39Z")
Any other solution I can try? ---
**Author:** ![rohitnagarro](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@rohitnagarro](https://discuss.elastic.co/u/rohitnagarro)\ **Post date:** [September 21, 2021, 10:40am UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473/11 "2021-09-21T10:40:17Z")
Thanks, I have tried with single primary shards, however response time we are getting is ~3 sec for 100 request in 4 sec. and Min: 18sec Max: 26.5sec for 1000 request in 30 sec Our target is 13k request in 1 min I am using Elasticsearch Search API "https://[deploymentname].[region].gcp.cloud.es.io:9243/[index]/\_search" ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 21, 2021, 10:49am UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473/12 "2021-09-21T10:49:34Z")
Your coordinating node is quite small so increasing its size to see if that makes any difference might be useful. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 19, 2021, 10:50am UTC](https://discuss.elastic.co/t/how-to-set-thread-pool-settings-for-all-data-nodes-in-7-14-elastic-cloud/284473/13 "2021-10-19T10:50:36Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.