# Scaling to 900 nodes or more, risks and pitfalls? **URL:** \ **Category:** Elasticsearch\ **Created:** [November 22, 2013, 3:28pm UTC](https://discuss.elastic.co/t/scaling-to-900-nodes-or-more-risks-and-pitfalls/14546 "2013-11-22T15:28:43Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Kim\_Laplume](https://avatars.discourse-cdn.com/v4/letter/k/f17d59/32.png) [@Kim\_Laplume](https://discuss.elastic.co/u/Kim_Laplume)\ **Post date:** [November 22, 2013, 3:28pm UTC](https://discuss.elastic.co/t/scaling-to-900-nodes-or-more-risks-and-pitfalls/14546/1 "2013-11-22T15:28:43Z")
Hi, the company I work for plans to scale our ES cluster from 20 nodes to about 900 or perhaps more, because of a higher data volume. Does anyone has experience with clusters of that size, is it even possible and can I expect the indexing and search time to be the same, increase or decrease. If it is possible, are there any pitfalls that one has to avoid? Best Regards, Kim -- 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:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [November 22, 2013, 9:38pm UTC](https://discuss.elastic.co/t/scaling-to-900-nodes-or-more-risks-and-pitfalls/14546/2 "2013-11-22T21:38:43Z")
Judging by others on the mailing list, I have not heard of a cluster of that size. Mozilla perhaps, but maybe not even them. Will all 900 nodes be part of the same cluster? The network chatter might be large. IMHO, if you can afford 900 nodes, then you can afford to use elasticsearch's own professional services. 🙂 Cheers, Ivan On Fri, Nov 22, 2013 at 7:28 AM, Kim Laplume [k.laplume@iterend.com](mailto:k.laplume@iterend.com) wrote: > Hi, > > the company I work for plans to scale our ES cluster from 20 nodes to > about 900 or perhaps more, because of a higher data volume. > > Does anyone has experience with clusters of that size, is it even possible > and can I expect the indexing and search time to be the same, increase or > decrease. > If it is possible, are there any pitfalls that one has to avoid? > > Best Regards, > > Kim > > -- > 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:** ![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, 2013, 11:01pm UTC](https://discuss.elastic.co/t/scaling-to-900-nodes-or-more-risks-and-pitfalls/14546/3 "2013-11-22T23:01:26Z")
Hi, I've heard of 1000-node SolrCloud indices that worked, so I assume ES may be OK there, too. I'd expect a good amount of work, careful configuring and tuning for such a massive system. How much data, what sort of data, and what sort of query complexity and rate are we talking about here? ## Otis Performance Monitoring \* Log Analytics \* Search Analytics Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/) On Friday, November 22, 2013 10:28:43 AM UTC-5, Kim Laplume wrote: > Hi, > > the company I work for plans to scale our ES cluster from 20 nodes to > about 900 or perhaps more, because of a higher data volume. > > Does anyone has experience with clusters of that size, is it even possible > and can I expect the indexing and search time to be the same, increase or > decrease. > If it is possible, are there any pitfalls that one has to avoid? > > Best Regards, > > Kim -- 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:** ![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 24, 2013, 10:27pm UTC](https://discuss.elastic.co/t/scaling-to-900-nodes-or-more-risks-and-pitfalls/14546/4 "2013-11-24T22:27:18Z")
Not directly related to ES cluster size, but still relevant to your goal; You'll want to invest time into something like Puppet/Chef and couple that with a module such as the ES puppet module, you'll find provisioning, extending and generally managing your cluster a lot simpler. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 23 November 2013 10:01, Otis Gospodnetic [otis.gospodnetic@gmail.com](mailto:otis.gospodnetic@gmail.com)wrote: > Hi, > > I've heard of 1000-node SolrCloud indices that worked, so I assume ES may > be OK there, too. I'd expect a good amount of work, careful configuring > and tuning for such a massive system. How much data, what sort of data, > and what sort of query complexity and rate are we talking about here? > > ## Otis > > Performance Monitoring \* Log Analytics \* Search Analytics > Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/) > > On Friday, November 22, 2013 10:28:43 AM UTC-5, Kim Laplume wrote: > > > Hi, > > > > the company I work for plans to scale our ES cluster from 20 nodes to > > about 900 or perhaps more, because of a higher data volume. > > > > Does anyone has experience with clusters of that size, is it even > > possible and can I expect the indexing and search time to be the same, > > increase or decrease. > > If it is possible, are there any pitfalls that one has to avoid? > > > > Best Regards, > > > > Kim > > -- > 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:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [November 24, 2013, 10:38pm UTC](https://discuss.elastic.co/t/scaling-to-900-nodes-or-more-risks-and-pitfalls/14546/5 "2013-11-24T22:38:53Z")
Yes, but you need to be careful not to let puppet/chef restart your nodes without proper coordination. Right now we use puppet for deployment and configuration but manually groom indexes off of each node before bouncing it. Sent from my iPhone > On Nov 24, 2013, at 5:27 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > > Not directly related to ES cluster size, but still relevant to your goal; You'll want to invest time into something like Puppet/Chef and couple that with a module such as the ES puppet module, you'll find provisioning, extending and generally managing your cluster a lot simpler. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > On 23 November 2013 10:01, Otis Gospodnetic [otis.gospodnetic@gmail.com](mailto:otis.gospodnetic@gmail.com) wrote: > > Hi, > > > > I've heard of 1000-node SolrCloud indices that worked, so I assume ES may be OK there, too. I'd expect a good amount of work, careful configuring and tuning for such a massive system. How much data, what sort of data, and what sort of query complexity and rate are we talking about here? > > > > ## Otis > > > > Performance Monitoring \* Log Analytics \* Search Analytics > > Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/) > > > > > On Friday, November 22, 2013 10:28:43 AM UTC-5, Kim Laplume wrote: > > > Hi, > > > > > > the company I work for plans to scale our ES cluster from 20 nodes to about 900 or perhaps more, because of a higher data volume. > > > > > > Does anyone has experience with clusters of that size, is it even possible and can I expect the indexing and search time to be the same, increase or decrease. > > > If it is possible, are there any pitfalls that one has to avoid? > > > > > > Best Regards, > > > > > > Kim > > > > -- > > 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). -- 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:** ![Kim\_Laplume\_2](https://avatars.discourse-cdn.com/v4/letter/k/a3d4f5/32.png) [@Kim\_Laplume\_2](https://discuss.elastic.co/u/Kim_Laplume_2)\ **Post date:** [November 27, 2013, 1:42pm UTC](https://discuss.elastic.co/t/scaling-to-900-nodes-or-more-risks-and-pitfalls/14546/6 "2013-11-27T13:42:52Z")
Thank you all for your feedback, I will take it into consideration On Sun, Nov 24, 2013 at 11:38 PM, Nik Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) wrote: > Yes, but you need to be careful not to let puppet/chef restart your nodes > without proper coordination. Right now we use puppet for deployment and > configuration but manually groom indexes off of each node before bouncing > it. > > Sent from my iPhone > > On Nov 24, 2013, at 5:27 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > wrote: > > Not directly related to ES cluster size, but still relevant to your goal; > You'll want to invest time into something like Puppet/Chef and couple that > with a module such as the ES puppet module, you'll find provisioning, > extending and generally managing your cluster a lot simpler. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 23 November 2013 10:01, Otis Gospodnetic [otis.gospodnetic@gmail.com](mailto:otis.gospodnetic@gmail.com)wrote: > > > Hi, > > > > I've heard of 1000-node SolrCloud indices that worked, so I assume ES may > > be OK there, too. I'd expect a good amount of work, careful configuring > > and tuning for such a massive system. How much data, what sort of data, > > and what sort of query complexity and rate are we talking about here? > > > > ## Otis > > > > Performance Monitoring \* Log Analytics \* Search Analytics > > Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/) > > > > On Friday, November 22, 2013 10:28:43 AM UTC-5, Kim Laplume wrote: > > > > > Hi, > > > > > > the company I work for plans to scale our ES cluster from 20 nodes to > > > about 900 or perhaps more, because of a higher data volume. > > > > > > Does anyone has experience with clusters of that size, is it even > > > possible and can I expect the indexing and search time to be the same, > > > increase or decrease. > > > If it is possible, are there any pitfalls that one has to avoid? > > > > > > Best Regards, > > > > > > Kim > > > > -- > > 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). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/EuuA50LHfrk/unsubscribe](https://groups.google.com/d/topic/elasticsearch/EuuA50LHfrk/unsubscribe). > To unsubscribe from this group and all its topics, 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). -- \*Kim Laplume \*| Software Engineer [kim@talkwalker.com](mailto:kim@talkwalker.com) [image: cid:image004.png@01CE19AF.C0122970] [http://www.talkwalker.com/](http://www.talkwalker.com/)[image: cid:image005.png@01CE19AF.C0122970] [https://www.facebook.com/talkwalker](https://www.facebook.com/talkwalker)[image: cid:image006.png@01CE19AF.C0122970] [https://twitter.com/talkwalker](https://twitter.com/talkwalker)[image: cid:image007.png@01CE19AF.C0122970][https://www.linkedin.com/company/talkwalker](https://www.linkedin.com/company/talkwalker)[image: cid:image008.png@01CE19AF.C0122970][https://plus.google.com/u/0/117412412458944231098/posts](https://plus.google.com/u/0/117412412458944231098/posts) A product of Trendiction S.A. 14, rue Aldringen | L- 1118 Luxembourg -- 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/CAEjR1hNY7AiC%2BGAd%3DRJDTH%3DTrakun6b-FQdOMi%3DoAWA6OgjiEQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEjR1hNY7AiC%2BGAd%3DRJDTH%3DTrakun6b-FQdOMi%3DoAWA6OgjiEQ%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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 27, 2013, 8:59pm UTC](https://discuss.elastic.co/t/scaling-to-900-nodes-or-more-risks-and-pitfalls/14546/7 "2013-11-27T20:59:21Z")
If you go ahead with this, I know there are a lot of people on the list (including me) that would be interested in keeping up to date with your progress. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 28 November 2013 00:42, Kim Laplume [kim@talkwalker.com](mailto:kim@talkwalker.com) wrote: > Thank you all for your feedback, I will take it into consideration > > On Sun, Nov 24, 2013 at 11:38 PM, Nik Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) wrote: > > > Yes, but you need to be careful not to let puppet/chef restart your nodes > > without proper coordination. Right now we use puppet for deployment and > > configuration but manually groom indexes off of each node before bouncing > > it. > > > > Sent from my iPhone > > > > On Nov 24, 2013, at 5:27 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > > wrote: > > > > Not directly related to ES cluster size, but still relevant to your goal; > > You'll want to invest time into something like Puppet/Chef and couple that > > with a module such as the ES puppet module, you'll find provisioning, > > extending and generally managing your cluster a lot simpler. > > > > Regards, > > Mark Walkom > > > > Infrastructure Engineer > > Campaign Monitor > > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > On 23 November 2013 10:01, Otis Gospodnetic [otis.gospodnetic@gmail.com](mailto:otis.gospodnetic@gmail.com)wrote: > > > > > Hi, > > > > > > I've heard of 1000-node SolrCloud indices that worked, so I assume ES > > > may be OK there, too. I'd expect a good amount of work, careful > > > configuring and tuning for such a massive system. How much data, what sort > > > of data, and what sort of query complexity and rate are we talking about > > > here? > > > > > > ## Otis > > > > > > Performance Monitoring \* Log Analytics \* Search Analytics > > > Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/) > > > > > > On Friday, November 22, 2013 10:28:43 AM UTC-5, Kim Laplume wrote: > > > > > > > Hi, > > > > > > > > the company I work for plans to scale our ES cluster from 20 nodes to > > > > about 900 or perhaps more, because of a higher data volume. > > > > > > > > Does anyone has experience with clusters of that size, is it even > > > > possible and can I expect the indexing and search time to be the same, > > > > increase or decrease. > > > > If it is possible, are there any pitfalls that one has to avoid? > > > > > > > > Best Regards, > > > > > > > > Kim > > > > > > -- > > > 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). > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/EuuA50LHfrk/unsubscribe](https://groups.google.com/d/topic/elasticsearch/EuuA50LHfrk/unsubscribe). > > To unsubscribe from this group and all its topics, 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). > > -- > > \*Kim Laplume \*| Software Engineer > > [kim@talkwalker.com](mailto:kim@talkwalker.com) > > [image: cid:image004.png@01CE19AF.C0122970] [http://www.talkwalker.com/](http://www.talkwalker.com/)[image: > cid:image005.png@01CE19AF.C0122970] [https://www.facebook.com/talkwalker](https://www.facebook.com/talkwalker)[image: > cid:image006.png@01CE19AF.C0122970] [https://twitter.com/talkwalker](https://twitter.com/talkwalker)[image: > cid:image007.png@01CE19AF.C0122970][https://www.linkedin.com/company/talkwalker](https://www.linkedin.com/company/talkwalker)[image: > cid:image008.png@01CE19AF.C0122970][https://plus.google.com/u/0/117412412458944231098/posts](https://plus.google.com/u/0/117412412458944231098/posts) > > A product of Trendiction S.A. > 14, rue Aldringen | L- 1118 Luxembourg > > -- > 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/CAEjR1hNY7AiC%2BGAd%3DRJDTH%3DTrakun6b-FQdOMi%3DoAWA6OgjiEQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEjR1hNY7AiC%2BGAd%3DRJDTH%3DTrakun6b-FQdOMi%3DoAWA6OgjiEQ%40mail.gmail.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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624ZmdK-ZCwBUQYv1UAGyucCMe\_cNCH2KCRv9Xdi6G%3D9ncg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZmdK-ZCwBUQYv1UAGyucCMe_cNCH2KCRv9Xdi6G%3D9ncg%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Laurent\_Laborde](https://avatars.discourse-cdn.com/v4/letter/l/e5b9ba/32.png) [@Laurent\_Laborde](https://discuss.elastic.co/u/Laurent_Laborde)\ **Post date:** [November 28, 2013, 7:40am UTC](https://discuss.elastic.co/t/scaling-to-900-nodes-or-more-risks-and-pitfalls/14546/8 "2013-11-28T07:40:11Z")
I can't imagine 1000 nodes (multi-PetaByte?) of full-text search so it probably is for bigdata. Why not create a lambda architecture ? Use elastcisearch for the serve layer (that's what i do) and hadoop as batch layer) to : - process/consolidate/query massive data in hadoop - use hadoop to create materialized view to elasticsearch : [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/overview/hadoop/) Create a speed layer for realtime data if needed. (eg : counter in redis) -- Laurent Laborde Bigdata Hacker On Wednesday, November 27, 2013 9:59:21 PM UTC+1, Mark Walkom wrote: > If you go ahead with this, I know there are a lot of people on the list > (including me) that would be interested in keeping up to date with your > progress. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \ > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 28 November 2013 00:42, Kim Laplume \<[k...@talkwalker.com](mailto:k...@talkwalker.com) \\>wrote: > > > Thank you all for your feedback, I will take it into consideration > > > > On Sun, Nov 24, 2013 at 11:38 PM, Nik Everett \<[nik...@gmail.com](mailto:nik...@gmail.com)\ > > > > > wrote: > > > > > Yes, but you need to be careful not to let puppet/chef restart your > > > nodes without proper coordination. Right now we use puppet for deployment > > > and configuration but manually groom indexes off of each node before > > > bouncing it. > > > > > > Sent from my iPhone > > > > > > On Nov 24, 2013, at 5:27 PM, Mark Walkom \<[ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com)\\> > > > wrote: > > > > > > Not directly related to ES cluster size, but still relevant to your > > > goal; You'll want to invest time into something like Puppet/Chef and couple > > > that with a module such as the ES puppet module, you'll find provisioning, > > > extending and generally managing your cluster a lot simpler. > > > > > > Regards, > > > Mark Walkom > > > > > > Infrastructure Engineer > > > Campaign Monitor > > > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \ > > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > > > On 23 November 2013 10:01, Otis Gospodnetic \<[otis.gos...@gmail.com](mailto:otis.gos...@gmail.com)\ > > > > > > > wrote: > > > > > > > Hi, > > > > > > > > I've heard of 1000-node SolrCloud indices that worked, so I assume ES > > > > may be OK there, too. I'd expect a good amount of work, careful > > > > configuring and tuning for such a massive system. How much data, what sort > > > > of data, and what sort of query complexity and rate are we talking about > > > > here? > > > > > > > > ## Otis > > > > > > > > Performance Monitoring \* Log Analytics \* Search Analytics > > > > Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/) > > > > > > > > On Friday, November 22, 2013 10:28:43 AM UTC-5, Kim Laplume wrote: > > > > > > > > > Hi, > > > > > > > > > > the company I work for plans to scale our ES cluster from 20 nodes to > > > > > about 900 or perhaps more, because of a higher data volume. > > > > > > > > > > Does anyone has experience with clusters of that size, is it even > > > > > possible and can I expect the indexing and search time to be the same, > > > > > increase or decrease. > > > > > If it is possible, are there any pitfalls that one has to avoid? > > > > > > > > > > Best Regards, > > > > > > > > > > Kim > > > > > > > > -- > > > > 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) \. > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@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 a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/EuuA50LHfrk/unsubscribe](https://groups.google.com/d/topic/elasticsearch/EuuA50LHfrk/unsubscribe). > > > To unsubscribe from this group and all its topics, send an email to > > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > -- > > > > \*Kim Laplume \*| Software Engineer > > > > [k...@talkwalker.com](mailto:k...@talkwalker.com) \ > > > > [image: cid:image004.png@01CE19AF.C0122970] [http://www.talkwalker.com/](http://www.talkwalker.com/)[image: > > cid:image005.png@01CE19AF.C0122970] [https://www.facebook.com/talkwalker](https://www.facebook.com/talkwalker)[image: > > cid:image006.png@01CE19AF.C0122970] [https://twitter.com/talkwalker](https://twitter.com/talkwalker)[image: > > cid:image007.png@01CE19AF.C0122970][https://www.linkedin.com/company/talkwalker](https://www.linkedin.com/company/talkwalker)[image: > > cid:image008.png@01CE19AF.C0122970][https://plus.google.com/u/0/117412412458944231098/posts](https://plus.google.com/u/0/117412412458944231098/posts) > > > > A product of Trendiction S.A. > > 14, rue Aldringen | L- 1118 Luxembourg > > > > -- > > 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) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAEjR1hNY7AiC%2BGAd%3DRJDTH%3DTrakun6b-FQdOMi%3DoAWA6OgjiEQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEjR1hNY7AiC%2BGAd%3DRJDTH%3DTrakun6b-FQdOMi%3DoAWA6OgjiEQ%40mail.gmail.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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/6ff7e2ea-d51f-484b-9a8f-dfdc57a5e0a6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6ff7e2ea-d51f-484b-9a8f-dfdc57a5e0a6%40googlegroups.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:04am UTC](https://discuss.elastic.co/t/scaling-to-900-nodes-or-more-risks-and-pitfalls/14546/9 "2017-07-06T02:04:22Z")