# Routing to replicas **URL:** \ **Category:** Elasticsearch\ **Created:** [November 3, 2013, 4:39pm UTC](https://discuss.elastic.co/t/routing-to-replicas/14234 "2013-11-03T16:39:23Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Val\_Vakar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/val_vakar/32/2017_2.png) [@Val\_Vakar](https://discuss.elastic.co/u/Val_Vakar)\ **Post date:** [November 3, 2013, 4:39pm UTC](https://discuss.elastic.co/t/routing-to-replicas/14234/1 "2013-11-03T16:39:23Z")
Hey guys, I have several indices with one replica each. I noticed that requests are sent to both replicas instead of one at a time, so the slower machine is always the bottleneck. Is there a way to route requests to one replica at a time? Thanks, Val -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [November 4, 2013, 8:42am UTC](https://discuss.elastic.co/t/routing-to-replicas/14234/2 "2013-11-04T08:42:20Z")
Hey, there is a routing option. However I am not yet sure, if that is what you want. You could use shard allocation to index new data into stronger machines, and then have a nightly cronjob which changes the index meta data, so it gets moved over to the weaker systems. Maybe this is what you want? References > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Hope this helps, otherwise ask more 🙂 --Alex On Sun, Nov 3, 2013 at 5:39 PM, Val Vakar [val.vakar@gmail.com](mailto:val.vakar@gmail.com) wrote: > Hey guys, > > I have several indices with one replica each. I noticed that requests are > sent to both replicas instead of one at a time, so the slower machine is > always the bottleneck. Is there a way to route requests to one replica at a > time? > > Thanks, > Val > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:09am UTC](https://discuss.elastic.co/t/routing-to-replicas/14234/3 "2017-07-06T02:09:05Z")