# Preparing for ElasticSearch in production **URL:** \ **Category:** Elasticsearch\ **Created:** [September 11, 2014, 7:17am UTC](https://discuss.elastic.co/t/preparing-for-elasticsearch-in-production/19732 "2014-09-11T07:17:41Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![James\_Ford](https://avatars.discourse-cdn.com/v4/letter/j/e0b2c6/32.png) [@James\_Ford](https://discuss.elastic.co/u/James_Ford)\ **Post date:** [September 11, 2014, 7:17am UTC](https://discuss.elastic.co/t/preparing-for-elasticsearch-in-production/19732/1 "2014-09-11T07:17:41Z")
Hello, I am wondering if it's a valid approach to start with a single-noded ElasticSearch cluster and then scale out when needed? This would of course involve a proper shard management. Thanks, -- 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/6826063f-c7a2-4782-a260-23881cde0c8d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6826063f-c7a2-4782-a260-23881cde0c8d%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [September 11, 2014, 8:47am UTC](https://discuss.elastic.co/t/preparing-for-elasticsearch-in-production/19732/2 "2014-09-11T08:47:31Z")
Sure. If you don't care at the beginning of your production about replication (and failover), that's perfectly fine. -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr Le 11 septembre 2014 à 09:17:44, Simon Forsberg ([simon.forsb@gmail.com](mailto:simon.forsb@gmail.com)) a écrit: Hello, I am wondering if it's a valid approach to start with a single-noded ElasticSearch cluster and then scale out when needed? This would of course involve a proper shard management. Thanks, -- 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/6826063f-c7a2-4782-a260-23881cde0c8d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6826063f-c7a2-4782-a260-23881cde0c8d%40googlegroups.com). 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/etPan.541161a3.74b0dc51.3c6%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.541161a3.74b0dc51.3c6%40MacBook-Air-de-David.local). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Benoit\_Gagnon](https://avatars.discourse-cdn.com/v4/letter/b/dbc845/32.png) [@Benoit\_Gagnon](https://discuss.elastic.co/u/Benoit_Gagnon)\ **Post date:** [September 14, 2014, 5:31pm UTC](https://discuss.elastic.co/t/preparing-for-elasticsearch-in-production/19732/3 "2014-09-14T17:31:14Z")
If you want the ability to do maintenance on your cluster without downtime, it will require at least two nodes. Even if you don't care about replication, and you don't expect your servers to fail, you could consider software/hardware upgrades as a form of failure tolerance. If spawning an occasional node to join your cluster is easy (with cloud virtualization for example), then it can possibly cover these maintenance scenarios. On Thursday, September 11, 2014 4:47:43 AM UTC-4, David Pilato wrote: > Sure. If you don't care at the beginning of your production about > replication (and failover), that's perfectly fine. > > -- > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_ > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > > Le 11 septembre 2014 à 09:17:44, Simon Forsberg ([simon...@gmail.com](mailto:simon...@gmail.com) > \) a écrit: > > Hello, > > I am wondering if it's a valid approach to start with a single-noded > Elasticsearch cluster and then scale out when needed? > > This would of course involve a proper shard management. > > Thanks, > > -- > 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/6826063f-c7a2-4782-a260-23881cde0c8d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6826063f-c7a2-4782-a260-23881cde0c8d%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/6826063f-c7a2-4782-a260-23881cde0c8d%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/6826063f-c7a2-4782-a260-23881cde0c8d%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/af100a6d-91ca-4e71-a56c-ff05983292c8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/af100a6d-91ca-4e71-a56c-ff05983292c8%40googlegroups.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, 1:02am UTC](https://discuss.elastic.co/t/preparing-for-elasticsearch-in-production/19732/4 "2017-07-06T01:02:28Z")
Closed on July 6, 2017, 1:02am UTC