# Prioritize search requests over index requests

**URL:** <https://discuss.elastic.co/t/prioritize-search-requests-over-index-requests/109201>\
**Category:** Elasticsearch\
**Created:** [November 27, 2017, 11:03am UTC](https://discuss.elastic.co/t/prioritize-search-requests-over-index-requests/109201 "2017-11-27T11:03:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![aslamy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aslamy/32/18254_2.png) [@aslamy](https://discuss.elastic.co/u/aslamy)\
**Post date:** [November 27, 2017, 11:03am UTC](https://discuss.elastic.co/t/prioritize-search-requests-over-index-requests/109201/1 "2017-11-27T11:03:14Z")

</div>

How can I force elasticsearch to always take care of search requests first then index requests.

---

<div class="post-metadata">

**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:** [November 27, 2017, 11:07am UTC](https://discuss.elastic.co/t/prioritize-search-requests-over-index-requests/109201/2 "2017-11-27T11:07:55Z")

</div>

You can not. They are served by different thread pools and you can not prioritise one over the other.

What is the problem you are having?

---

<div class="post-metadata">

**Author:** ![aslamy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aslamy/32/18254_2.png) [@aslamy](https://discuss.elastic.co/u/aslamy)\
**Post date:** [November 27, 2017, 11:14am UTC](https://discuss.elastic.co/t/prioritize-search-requests-over-index-requests/109201/3 "2017-11-27T11:14:05Z")

</div>

But maybe it's possible to give more resources to search requests. CPU, RAM etc.

The problem is that I need to search and index at the same time. This increase search response time. Because elasticsearch is busy with indexing,.

---

<div class="post-metadata">

**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:** [November 27, 2017, 11:17am UTC](https://discuss.elastic.co/t/prioritize-search-requests-over-index-requests/109201/4 "2017-11-27T11:17:17Z")

</div>

You might be able to achieve this by [reducing the size of the index and bulk thread pools](https://www.elastic.co/guide/en/elasticsearch/reference/6.0/modules-threadpool.html), but that would lead to a constant limitation, not prioritisation. I don't think you can allocate other types of resources across different tasks.

---

<div class="post-metadata">

**Author:** ![aslamy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aslamy/32/18254_2.png) [@aslamy](https://discuss.elastic.co/u/aslamy)\
**Post date:** [November 27, 2017, 11:20am UTC](https://discuss.elastic.co/t/prioritize-search-requests-over-index-requests/109201/5 "2017-11-27T11:20:57Z")

</div>

Ok thank you Christian.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 25, 2017, 11:21am UTC](https://discuss.elastic.co/t/prioritize-search-requests-over-index-requests/109201/6 "2017-12-25T11:21:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.