# Index load distribution

**URL:** <https://discuss.elastic.co/t/index-load-distribution/20886>\
**Category:** Elasticsearch\
**Created:** [November 21, 2014, 10:00am UTC](https://discuss.elastic.co/t/index-load-distribution/20886 "2014-11-21T10:00:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ivan\_Gonzalez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ivan_gonzalez/32/40341_2.png) [@Ivan\_Gonzalez](https://discuss.elastic.co/u/Ivan_Gonzalez)\
**Post date:** [November 21, 2014, 10:00am UTC](https://discuss.elastic.co/t/index-load-distribution/20886/1 "2014-11-21T10:00:30Z")

</div>

Hello,

I have been using ES for a year and I am very happy with the performance  
and its powerful filtering, but now I have to index 50millions records and  
I am a bit worried by the performance in general.

Attending to the doc I undestand that if I setup two new nodes (aws) more  
for that new big index, all the caching/load for that index will be held  
only in that two new nodes.

There hare three main (\<3gb) indexes which are performing well with lots of  
queries and this performance should not be degraded by adding the new index.

I would like to confirm if my assumption is correct or if some of the load  
for that index searches/cache/etc will be passed to the other nodes which  
manages the three main indexes.

Thank you all very much in advance!!

--  
Ivan  
DevOp - IT Manager at [Trovimap.com](http://Trovimap.com)

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/31d1e52e-194d-40bb-b33f-a86ffdd8b9a8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/31d1e52e-194d-40bb-b33f-a86ffdd8b9a8%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [November 21, 2014, 10:20pm UTC](https://discuss.elastic.co/t/index-load-distribution/20886/2 "2014-11-21T22:20:38Z")

</div>

ES scales horizontally, so the more nodes you add the better it can perform.  
So yes your logic is correct, though you are better off using three nodes  
as it minimises the risk of a split cluster.

On 21 November 2014 21:00, Iván González [igonzalezvaliente@gmail.com](mailto:igonzalezvaliente@gmail.com)  
wrote:

> Hello,
> 
> I have been using ES for a year and I am very happy with the performance  
> and its powerful filtering, but now I have to index 50millions records and  
> I am a bit worried by the performance in general.
> 
> Attending to the doc I undestand that if I setup two new nodes (aws) more  
> for that new big index, all the caching/load for that index will be held  
> only in that two new nodes.
> 
> There hare three main (\<3gb) indexes which are performing well with lots  
> of queries and this performance should not be degraded by adding the new  
> index.
> 
> I would like to confirm if my assumption is correct or if some of the load  
> for that index searches/cache/etc will be passed to the other nodes which  
> manages the three main indexes.
> 
> Thank you all very much in advance!!
> 
> --  
> Ivan  
> DevOp - IT Manager at [Trovimap.com](http://Trovimap.com)
> 
> --  
> 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).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/31d1e52e-194d-40bb-b33f-a86ffdd8b9a8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/31d1e52e-194d-40bb-b33f-a86ffdd8b9a8%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/31d1e52e-194d-40bb-b33f-a86ffdd8b9a8%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/31d1e52e-194d-40bb-b33f-a86ffdd8b9a8%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZkKF0THEc1pKc30MGRZk4\_5C1kcgLDmtjADEqZOxXdm1A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZkKF0THEc1pKc30MGRZk4_5C1kcgLDmtjADEqZOxXdm1A%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\
**Post date:** [November 22, 2014, 4:33pm UTC](https://discuss.elastic.co/t/index-load-distribution/20886/3 "2014-11-22T16:33:09Z")

</div>

To add to Mark's comment - you'll obviously want to makes sure your cluster  
is more or less balanced (in terms of shards, their sizes, etc.). Should  
happen automatically, but we've seen a number of situations where things  
were not working well because shards were not quite balanced, so you may  
want to have a peek at this after you add more nodes.

## Otis

Monitoring \* Alerting \* Anomaly Detection \* Centralized Log Management  
Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/)

On Friday, November 21, 2014 5:21:27 PM UTC-5, Mark Walkom wrote:

> ES scales horizontally, so the more nodes you add the better it can  
> perform.  
> So yes your logic is correct, though you are better off using three nodes  
> as it minimises the risk of a split cluster.
> 
> On 21 November 2014 21:00, Iván González \<[igonzale...@gmail.com](mailto:igonzale...@gmail.com)  
> \<javascript:\>\> wrote:
> 
> > Hello,
> > 
> > I have been using ES for a year and I am very happy with the performance  
> > and its powerful filtering, but now I have to index 50millions records and  
> > I am a bit worried by the performance in general.
> > 
> > Attending to the doc I undestand that if I setup two new nodes (aws) more  
> > for that new big index, all the caching/load for that index will be held  
> > only in that two new nodes.
> > 
> > There hare three main (\<3gb) indexes which are performing well with lots  
> > of queries and this performance should not be degraded by adding the new  
> > index.
> > 
> > I would like to confirm if my assumption is correct or if some of the  
> > load for that index searches/cache/etc will be passed to the other nodes  
> > which manages the three main indexes.
> > 
> > Thank you all very much in advance!!
> > 
> > --  
> > Ivan  
> > DevOp - IT Manager at [Trovimap.com](http://Trovimap.com)
> > 
> > --  
> > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/31d1e52e-194d-40bb-b33f-a86ffdd8b9a8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/31d1e52e-194d-40bb-b33f-a86ffdd8b9a8%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/31d1e52e-194d-40bb-b33f-a86ffdd8b9a8%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/31d1e52e-194d-40bb-b33f-a86ffdd8b9a8%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/23883053-38ac-4b0a-b8d6-54f6c8ac1013%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/23883053-38ac-4b0a-b8d6-54f6c8ac1013%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 12:48am UTC](https://discuss.elastic.co/t/index-load-distribution/20886/4 "2017-07-06T00:48:19Z")

</div>