# Separate of read and write indices

**URL:** <https://discuss.elastic.co/t/separate-of-read-and-write-indices/148608>\
**Category:** Elasticsearch\
**Created:** [September 14, 2018, 10:49am UTC](https://discuss.elastic.co/t/separate-of-read-and-write-indices/148608 "2018-09-14T10:49:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kannan\_raj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kannan_raj/32/63201_2.png) [@kannan\_raj](https://discuss.elastic.co/u/kannan_raj)\
**Post date:** [September 14, 2018, 10:49am UTC](https://discuss.elastic.co/t/separate-of-read-and-write-indices/148608/1 "2018-09-14T10:49:47Z")

</div>

is there any way to setup separate readonly schema and write schema.

---

<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:** [September 14, 2018, 10:51am UTC](https://discuss.elastic.co/t/separate-of-read-and-write-indices/148608/2 "2018-09-14T10:51:32Z")

</div>

Not really, you can't write to one index and then have the write magically appear in another index without a similar write.

What are you trying to do?

---

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [September 14, 2018, 11:00am UTC](https://discuss.elastic.co/t/separate-of-read-and-write-indices/148608/3 "2018-09-14T11:00:31Z")

</div>

Snapshot restore?

Snapshot from the write store and restore into the read-only one.  
These operations should be incremental so that only segments with new writes are copied over (plus also any segments rewritten as part of merge operations).  
Obviously this would be high latency of updates as you'd only do this operation ever so often to allow the read-only store to "catch up" with the write-enabled store.

I have no direct experience of employing this technique so will leave it to others to comment on its effectiveness.

---

<div class="post-metadata">

**Author:** ![kannan\_raj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kannan_raj/32/63201_2.png) [@kannan\_raj](https://discuss.elastic.co/u/kannan_raj)\
**Post date:** [September 18, 2018, 9:12am UTC](https://discuss.elastic.co/t/separate-of-read-and-write-indices/148608/4 "2018-09-18T09:12:00Z")

</div>

i would trying to separate operation to get better performance, log stash will be pointing to write index and the same time kibana will be pointing into read only index.

---

<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:** [September 18, 2018, 9:14am UTC](https://discuss.elastic.co/t/separate-of-read-and-write-indices/148608/5 "2018-09-18T09:14:09Z")

</div>

Sure, but you still need to write to the "read only" index, so it's doing the same amount of work as the "write only" index anyway. Adding reads isn't going to make any magic difference.

---

<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 16, 2018, 9:14am UTC](https://discuss.elastic.co/t/separate-of-read-and-write-indices/148608/6 "2018-10-16T09:14:16Z")

</div>

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