# Read only indices

**URL:** <https://discuss.elastic.co/t/read-only-indices/148705>\
**Category:** Elasticsearch\
**Created:** [September 15, 2018, 1:39pm UTC](https://discuss.elastic.co/t/read-only-indices/148705 "2018-09-15T13:39:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Itay\_Bittan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itay_bittan/32/23527_2.png) [@Itay\_Bittan](https://discuss.elastic.co/u/Itay_Bittan)\
**Post date:** [September 15, 2018, 1:39pm UTC](https://discuss.elastic.co/t/read-only-indices/148705/1 "2018-09-15T13:39:59Z")

</div>

I'm running with Elasticsearch 6.3.0.  
First I'm preparing my indices (by indexing them with bulks) and then when they are ready, we are not updating them anymore, we are only querying / searching / serving from them (with very high load).

My questions are:

- Can I set refresh\_interval to -1 (disabling it) from the beginning and refresh with each bulk operation (as part of my indexing stage)?
- Can I keep the refresh\_interval disabled when the index is serving mode?
- After finishing the indexing process, and before moving it to serving mode, is it ok to set the index.blocks.write to true and force merge and keeping it as read only for the serving mode?
- is any of the above changed if i'm changing the replication\_factor (increasing it) later on in serving mode?

Thanks,  
Itay

---

<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:** [October 13, 2018, 1:40pm UTC](https://discuss.elastic.co/t/read-only-indices/148705/2 "2018-10-13T13:40:04Z")

</div>

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