# Cannot set thread\_pool setting in Elastic Cloud user settings

**URL:** <https://discuss.elastic.co/t/cannot-set-thread-pool-setting-in-elastic-cloud-user-settings/164239>\
**Category:** Elasticsearch\
**Created:** [January 15, 2019, 5:43am UTC](https://discuss.elastic.co/t/cannot-set-thread-pool-setting-in-elastic-cloud-user-settings/164239 "2019-01-15T05:43:06Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 15, 2019, 5:48am UTC](https://discuss.elastic.co/t/cannot-set-thread-pool-setting-in-elastic-cloud-user-settings/164239/2 "2019-01-15T05:48:02Z")

</div>

> [@CapitanRedBeard](#):
>
> The general consensus seems to be bumping the queue\_size so requests don't get dropped

Dunno where you are getting that consensus from, but I would be confident in saying that it's not the best idea. Have a read of [Any idea what these errors mean version 2.4.2 - #5 by jasontedor](https://discuss.elastic.co/t/any-idea-what-these-errors-mean-version-2-4-2/70690/5)

If you are using the Elasticsearch Service then you can increase the size of the cluster when you are sending these requests, then downsize when done.  
Or you can throttle things in your client when you get a 429.

---

_[View the full topic](https://discuss.elastic.co/t/cannot-set-thread-pool-setting-in-elastic-cloud-user-settings/164239)._