# Searching and indexing priority **URL:** \ **Category:** Elasticsearch\ **Created:** [September 10, 2020, 12:04pm UTC](https://discuss.elastic.co/t/searching-and-indexing-priority/248166 "2020-09-10T12:04:35Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ssiws](https://avatars.discourse-cdn.com/v4/letter/s/4af34b/32.png) [@ssiws](https://discuss.elastic.co/u/ssiws)\ **Post date:** [September 10, 2020, 12:04pm UTC](https://discuss.elastic.co/t/searching-and-indexing-priority/248166/1 "2020-09-10T12:04:35Z")
Hello, generally speaking, how does Elasticsearch handles searching "priority" while indexing ? I noticed that when someone performs a query with a timerange of multiple weeks, indexing almost halts while the query is running. I find it odd that the indexing process can be disrupted by read queries. Thanks, best regards ---
**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 10, 2020, 7:56pm UTC](https://discuss.elastic.co/t/searching-and-indexing-priority/248166/2 "2020-09-10T19:56:11Z")
As far as I know there is no defined or configurable priority, so reads and writes to the cluster will affect each other and compete for the same resources. A lot of use cases are more focussed on search than ingestion, so would likely make the opposite argument that ingest should be allowed to affect queries. There is therefore no defined priority that would fit everyone as it would depend a lot on the use case. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 8, 2020, 7:56pm UTC](https://discuss.elastic.co/t/searching-and-indexing-priority/248166/3 "2020-10-08T19:56:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.