Preparing for ElasticSearch in production

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/6826063f-c7a2-4782-a260-23881cde0c8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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
@dadoonet | @elasticsearchfr

Le 11 septembre 2014 à 09:17:44, Simon Forsberg (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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/6826063f-c7a2-4782-a260-23881cde0c8d%40googlegroups.com.
For more options, visit 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.
To view this discussion on the web visit 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.

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
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr

Le 11 septembre 2014 à 09:17:44, Simon Forsberg (simon...@gmail.com
<javascript:>) 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 <javascript:>.
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?utm_medium=email&utm_source=footer
.
For more options, visit 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/af100a6d-91ca-4e71-a56c-ff05983292c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.