# Read-Only On Replica

**URL:** <https://discuss.elastic.co/t/read-only-on-replica/214200>\
**Category:** Elasticsearch\
**Created:** [January 8, 2020, 9:38am UTC](https://discuss.elastic.co/t/read-only-on-replica/214200 "2020-01-08T09:38:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cigarl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cigarl/32/56745_2.png) [@cigarl](https://discuss.elastic.co/u/cigarl)\
**Post date:** [January 8, 2020, 9:38am UTC](https://discuss.elastic.co/t/read-only-on-replica/214200/1 "2020-01-08T09:38:35Z")

</div>

If the primary shard and the replica share the same data files, and make the copy read-only. What is the best way to use ？

I found that the engine was initialized based on the index level when the node started. Whether the read-only engine can be used for the replica in _IndexShard_, and the engine initialized at node startup can be discarded？

Are there any other risks besides data loss？

I just want the replica to be read-only.

---

<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:** [February 5, 2020, 9:38am UTC](https://discuss.elastic.co/t/read-only-on-replica/214200/2 "2020-02-05T09:38:39Z")

</div>

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