# Use replica for read-only access and "original" for read & write access **URL:** \ **Category:** Elasticsearch\ **Created:** [September 30, 2012, 10:21pm UTC](https://discuss.elastic.co/t/use-replica-for-read-only-access-and-original-for-read-write-access/9197 "2012-09-30T22:21:37Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![anon44344346](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@anon44344346](https://discuss.elastic.co/u/anon44344346)\ **Post date:** [September 30, 2012, 10:21pm UTC](https://discuss.elastic.co/t/use-replica-for-read-only-access-and-original-for-read-write-access/9197/1 "2012-09-30T22:21:37Z")
Throwing some stones around here. We have an elastisearch in place, with about 120 indexes (two per customer) that need to be updated with a daily feed. This means reindexing for every index at least once a day, which is costly. I know there are other means of optimizing this, such as bulk indexing. Anyway, in some sharded/distributed systems, one classical optimization step is -given you have a "master" and a "slave" database server, by instance- is to use the "master" server for reading/writing (mostly through a supposed admin interface), and to use the "slave" server for read access only. I was wondering if is there any way of achieving this with the elasticsearch replicas, maybe setting a few as "read-only" and then redirecting all search request to these??? Looks like this is not likely to be possible, but it was worth the shot. 😉 -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:10am UTC](https://discuss.elastic.co/t/use-replica-for-read-only-access-and-original-for-read-write-access/9197/2 "2017-07-06T03:10:43Z")