# Scale Out Best Practices / How to **URL:** \ **Category:** Elasticsearch\ **Created:** [February 13, 2015, 10:44pm UTC](https://discuss.elastic.co/t/scale-out-best-practices-how-to/22164 "2015-02-13T22:44:07Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Garrett\_Johnson](https://avatars.discourse-cdn.com/v4/letter/g/41988e/32.png) [@Garrett\_Johnson](https://discuss.elastic.co/u/Garrett_Johnson)\ **Post date:** [February 13, 2015, 10:44pm UTC](https://discuss.elastic.co/t/scale-out-best-practices-how-to/22164/1 "2015-02-13T22:44:07Z")
Is there a How to guide along with best practices for Scale Out? I have a single instance server of Elastic Search and I would like to scale out. From other posts in this group I have tried with no success to add an additional server into the group. This additional server is not on the same domain it's [hostname.DIT.mydomain.com](http://hostname.DIT.mydomain.com) vs. [hostname2.SIT.mydomain.com](http://hostname2.SIT.mydomain.com) Other than it just not working for me at this point, I'm concerned because if I have to edit the elasticsearch.yml file that means I must bring down that instance. If I end up with 1,2,3,4,10,20,30,40 nodes. How do I not bring them all down for any changes. I'm sure there are different practices like a Master that in the 40 case you would keep up all the time and only upgrade each one individually. How do you handle this with upgrades etc. -- 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/7617be7a-1590-4651-9c46-83470ee448be%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7617be7a-1590-4651-9c46-83470ee448be%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [February 16, 2015, 9:02am UTC](https://discuss.elastic.co/t/scale-out-best-practices-how-to/22164/2 "2015-02-16T09:02:38Z")
(I couldn't find your other posts on scaling?) As long as your nodes can talk to each other then you should be ok. However if you are thinking about running cross DC clusters (reading between the lines based on your hostname convention), then that is not recommended. The rest of your question is based on how you expect to grow, but until you get to more than 1 node you are probably going to have to restart your current one. On 14 February 2015 at 09:44, GWired [garrettcjohnson@gmail.com](mailto:garrettcjohnson@gmail.com) wrote: > Is there a How to guide along with best practices for Scale Out? > > I have a single instance server of Elastic Search and I would like to > scale out. > > From other posts in this group I have tried with no success to add an > additional server into the group. > > This additional server is not on the same domain it's > [hostname.DIT.mydomain.com](http://hostname.DIT.mydomain.com) vs. [hostname2.SIT.mydomain.com](http://hostname2.SIT.mydomain.com) > > Other than it just not working for me at this point, I'm concerned because > if I have to edit the elasticsearch.yml file that means I must bring down > that instance. > > If I end up with 1,2,3,4,10,20,30,40 nodes. How do I not bring them all > down for any changes. I'm sure there are different practices like a Master > that in the 40 case you would keep up all the time and only upgrade each > one individually. > > How do you handle this with upgrades etc. > > -- > 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/7617be7a-1590-4651-9c46-83470ee448be%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7617be7a-1590-4651-9c46-83470ee448be%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/7617be7a-1590-4651-9c46-83470ee448be%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7617be7a-1590-4651-9c46-83470ee448be%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/CAEYi1X\_jgGLBehF5znKfe3PfqqcuTpZbMzNLEFZ-tT\_rudQr%2Bw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_jgGLBehF5znKfe3PfqqcuTpZbMzNLEFZ-tT_rudQr%2Bw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Garrett\_Johnson](https://avatars.discourse-cdn.com/v4/letter/g/41988e/32.png) [@Garrett\_Johnson](https://discuss.elastic.co/u/Garrett_Johnson)\ **Post date:** [February 16, 2015, 2:02pm UTC](https://discuss.elastic.co/t/scale-out-best-practices-how-to/22164/3 "2015-02-16T14:02:23Z")
Are you saying it is not recommended to host across Data Centers? How do you provide High Availability if one Data Center goes down? And reading between the lines on more than 1 node issue. I'm guessing you are saying that once I have multiple nodes I can bring them up and down as needed. Really having a hard time understanding plugins in this scenario. I don't want every server in the cluster to be executing say the jdbc river do I? I only want one to be running it and then in the event that one goes down another would pick it up. As far as I know there isn't any altering system. On Monday, February 16, 2015 at 4:03:11 AM UTC-5, Mark Walkom wrote: > (I couldn't find your other posts on scaling?) > > As long as your nodes can talk to each other then you should be ok. > However if you are thinking about running cross DC clusters (reading > between the lines based on your hostname convention), then that is not > recommended. > > The rest of your question is based on how you expect to grow, but until > you get to more than 1 node you are probably going to have to restart your > current one. > > On 14 February 2015 at 09:44, GWired \<[garrett...@gmail.com](mailto:garrett...@gmail.com) \\> > wrote: > > > Is there a How to guide along with best practices for Scale Out? > > > > I have a single instance server of Elastic Search and I would like to > > scale out. > > > > From other posts in this group I have tried with no success to add an > > additional server into the group. > > > > This additional server is not on the same domain it's > > [hostname.DIT.mydomain.com](http://hostname.DIT.mydomain.com) vs. [hostname2.SIT.mydomain.com](http://hostname2.SIT.mydomain.com) > > > > Other than it just not working for me at this point, I'm concerned > > because if I have to edit the elasticsearch.yml file that means I must > > bring down that instance. > > > > If I end up with 1,2,3,4,10,20,30,40 nodes. How do I not bring them all > > down for any changes. I'm sure there are different practices like a Master > > that in the 40 case you would keep up all the time and only upgrade each > > one individually. > > > > How do you handle this with upgrades etc. > > > > -- > > 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/7617be7a-1590-4651-9c46-83470ee448be%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7617be7a-1590-4651-9c46-83470ee448be%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/7617be7a-1590-4651-9c46-83470ee448be%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7617be7a-1590-4651-9c46-83470ee448be%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/1bcb86b3-7833-4afa-a5b5-66408b325b9a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1bcb86b3-7833-4afa-a5b5-66408b325b9a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [February 16, 2015, 9:36pm UTC](https://discuss.elastic.co/t/scale-out-best-practices-how-to/22164/4 "2015-02-16T21:36:18Z")
Yes, that is what I am saying. ES is latency sensitive and betting against that can potentially cause problem. You are better off using snapshot+restore or using your indexing method to send to both clusters. As for plugins, some require all nodes to run them, some don't. Ultimately this comes down to what the plugin does and you have to work around/with it. On 17 February 2015 at 01:02, GWired [garrettcjohnson@gmail.com](mailto:garrettcjohnson@gmail.com) wrote: > Are you saying it is not recommended to host across Data Centers? > > How do you provide High Availability if one Data Center goes down? > > And reading between the lines on more than 1 node issue. I'm guessing you > are saying that once I have multiple nodes I can bring them up and down as > needed. Really having a hard time understanding plugins in this scenario. > I don't want every server in the cluster to be executing say the jdbc river > do I? I only want one to be running it and then in the event that one > goes down another would pick it up. As far as I know there isn't any > altering system. > > On Monday, February 16, 2015 at 4:03:11 AM UTC-5, Mark Walkom wrote: > > > (I couldn't find your other posts on scaling?) > > > > As long as your nodes can talk to each other then you should be ok. > > However if you are thinking about running cross DC clusters (reading > > between the lines based on your hostname convention), then that is not > > recommended. > > > > The rest of your question is based on how you expect to grow, but until > > you get to more than 1 node you are probably going to have to restart your > > current one. > > > > On 14 February 2015 at 09:44, GWired [garrett...@gmail.com](mailto:garrett...@gmail.com) wrote: > > > > > Is there a How to guide along with best practices for Scale Out? > > > > > > I have a single instance server of Elastic Search and I would like to > > > scale out. > > > > > > From other posts in this group I have tried with no success to add an > > > additional server into the group. > > > > > > This additional server is not on the same domain it's > > > [hostname.DIT.mydomain.com](http://hostname.DIT.mydomain.com) vs. [hostname2.SIT.mydomain.com](http://hostname2.SIT.mydomain.com) > > > > > > Other than it just not working for me at this point, I'm concerned > > > because if I have to edit the elasticsearch.yml file that means I must > > > bring down that instance. > > > > > > If I end up with 1,2,3,4,10,20,30,40 nodes. How do I not bring them all > > > down for any changes. I'm sure there are different practices like a Master > > > that in the 40 case you would keep up all the time and only upgrade each > > > one individually. > > > > > > How do you handle this with upgrades etc. > > > > > > -- > > > 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/](https://groups.google.com/d/) > > > msgid/elasticsearch/7617be7a-1590-4651-9c46-83470ee448be% > > > [40googlegroups.com](http://40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/7617be7a-1590-4651-9c46-83470ee448be%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7617be7a-1590-4651-9c46-83470ee448be%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/1bcb86b3-7833-4afa-a5b5-66408b325b9a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1bcb86b3-7833-4afa-a5b5-66408b325b9a%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/1bcb86b3-7833-4afa-a5b5-66408b325b9a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1bcb86b3-7833-4afa-a5b5-66408b325b9a%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/CAEYi1X\_D5qn3bRjHp74Ms9zrNa2JOn19pOaT5OJfjaRZgu-%3D1A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_D5qn3bRjHp74Ms9zrNa2JOn19pOaT5OJfjaRZgu-%3D1A%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:32am UTC](https://discuss.elastic.co/t/scale-out-best-practices-how-to/22164/5 "2017-07-06T00:32:20Z")