# Moving to production considerations - applications with their clusters' infrastructure

**URL:** <https://discuss.elastic.co/t/moving-to-production-considerations-applications-with-their-clusters-infrastructure/22136>\
**Category:** Elasticsearch\
**Created:** [February 12, 2015, 2:27pm UTC](https://discuss.elastic.co/t/moving-to-production-considerations-applications-with-their-clusters-infrastructure/22136 "2015-02-12T14:27:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rondelvictor](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@rondelvictor](https://discuss.elastic.co/u/rondelvictor)\
**Post date:** [February 12, 2015, 2:27pm UTC](https://discuss.elastic.co/t/moving-to-production-considerations-applications-with-their-clusters-infrastructure/22136/1 "2015-02-12T14:27:46Z")

</div>

Hi everyone,

I am considering moving one or several elasticsearch clusters to production.  
Although Elasticsearch's documentation and community is _great_, I am  
strongly startled not to find any _complete use-case story_ stretching from  
application(s) needs and data considerations to hardware ones.  
Indeed, I understand why "what/how much hardware / configuration /  
sharding" questions are systematically replied with both "it depends"  
followed by "test".  
But then, what about a few complete descriptions, out of so many  
elasticsearch users, from data use case to cluster's internals, along with  
a few performance and nodes stats?

So here are questions, before moving to production :

Are there any _complete_ use cases around? Could you share some? By  
complete I mean including _at least some_ of the following :

1. _Application needs and scope_
2. _Indexing Data indications_ : data volume, documents mapping,  
documents / indexes volume
3. _Searching Data indications_ : different applications, queries, use  
of facets - filters - aggregations, concurrent indexing
4. _Cluster Hardware_ : machines' hardware (RAM, Disks/SSD -  
DAS-JBOD/SAN/NAS), JVM heap / OS Cache, nb of machines, back office network
5. _Cluster Configuration_ : one or several indexes, sharding,  
replication, master nodes, data nodes, use of over-sharding at start-up,  
use of re-indexing
6. \*Benchmaks \*: queries response times, QPS, with or without concurrent  
indexing, memory heap sweet spot, nodes stats

For those interested, here are the (not _complete_) best-among-very-few  
exemples I've stumbled upon so far :

- The very best (perfs with hardware and query description) :  
[http://fr.slideshare.net/charliejuggler/lucene-solrlondonug-meetup28nov2014-solr-es-performance](http://fr.slideshare.net/charliejuggler/lucene-solrlondonug-meetup28nov2014-solr-es-performance)
- Hardware and master nodes heap :  
[https://groups.google.com/forum/?fromgroups#!searchin/elasticsearch/sizing/elasticsearch/V5BtrCGOqoU/l7x6vqMEx5YJ](https://groups.google.com/forum/?fromgroups#!searchin/elasticsearch/sizing/elasticsearch/V5BtrCGOqoU/l7x6vqMEx5YJ)
- _6th slide_ - Hardware and storage with number of documents (well,  
without indexes and documents storage volume nor RAM consumption) :

[https://speakerdeck.com/bhaskarvk/scaling-elasticsearch-washington-dc-meetup](https://speakerdeck.com/bhaskarvk/scaling-elasticsearch-washington-dc-meetup)  
With JBOD / SAN storage discussion in "To Raid or not to Raid":

[https://groups.google.com/forum/?fromgroups#!searchin/elasticsearch/hardware/elasticsearch/HSj2fZGdU1Y/4mFCBTCb-JcJ](https://groups.google.com/forum/?fromgroups#!searchin/elasticsearch/hardware/elasticsearch/HSj2fZGdU1Y/4mFCBTCb-JcJ)

- Usual heap considerations in a real case :

[https://codeascraft.com/2014/12/04/juggling-multiple-elasticsearch-instances-on-a-single-host/](https://codeascraft.com/2014/12/04/juggling-multiple-elasticsearch-instances-on-a-single-host/)

Do not forget Elasticsearch awesome docs for moving to production  
considerations :

- 

## [http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/administration.html](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/administration.html)

## [http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/deploy.html](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/deploy.html)

## _[http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/hardware.html](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/hardware.html)_

_[http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/heap-sizing.html](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/heap-sizing.html)_

--  
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/927f60b1-8ae2-463e-b725-5f4f993905d9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/927f60b1-8ae2-463e-b725-5f4f993905d9%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Charlie\_Hull](https://avatars.discourse-cdn.com/v4/letter/c/6f9a4e/32.png) [@Charlie\_Hull](https://discuss.elastic.co/u/Charlie_Hull)\
**Post date:** [February 13, 2015, 3:06pm UTC](https://discuss.elastic.co/t/moving-to-production-considerations-applications-with-their-clusters-infrastructure/22136/2 "2015-02-13T15:06:49Z")

</div>

Hi,

Firstly, thanks for the kind words about the performance study: we're  
hoping to revisit this soon after the feedback we've had on better tuning  
for each engine. I agree there's a paucity of studies, but in a month or  
two we should have one from a project we're working on to build an index of  
product data - we hope to present this at the London Meetup group but will  
publish the slides afterwards. Sorry this is in the future!

Cheers

Charlie

On 12 February 2015 at 14:27, [rondelvictor@gmail.com](mailto:rondelvictor@gmail.com) wrote:

> Hi everyone,
> 
> I am considering moving one or several elasticsearch clusters to  
> production.  
> Although Elasticsearch's documentation and community is _great_, I am  
> strongly startled not to find any _complete use-case story_ stretching  
> from application(s) needs and data considerations to hardware ones.  
> Indeed, I understand why "what/how much hardware / configuration /  
> sharding" questions are systematically replied with both "it depends"  
> followed by "test".  
> But then, what about a few complete descriptions, out of so many  
> elasticsearch users, from data use case to cluster's internals, along with  
> a few performance and nodes stats?
> 
> So here are questions, before moving to production :
> 
> Are there any _complete_ use cases around? Could you share some? By  
> complete I mean including _at least some_ of the following :
> 
> 1. _Application needs and scope_
> 2. _Indexing Data indications_ : data volume, documents mapping,  
> documents / indexes volume
> 3. _Searching Data indications_ : different applications, queries, use  
> of facets - filters - aggregations, concurrent indexing
> 4. _Cluster Hardware_ : machines' hardware (RAM, Disks/SSD -  
> DAS-JBOD/SAN/NAS), JVM heap / OS Cache, nb of machines, back office network
> 5. _Cluster Configuration_ : one or several indexes, sharding,  
> replication, master nodes, data nodes, use of over-sharding at start-up,  
> use of re-indexing
> 6. \*Benchmaks \*: queries response times, QPS, with or without  
> concurrent indexing, memory heap sweet spot, nodes stats
> 
> For those interested, here are the (not _complete_) best-among-very-few  
> exemples I've stumbled upon so far :
> 
> - The very best (perfs with hardware and query description) :  
> [Solr and Elasticsearch, a performance study | PPT](http://fr.slideshare.net/charliejuggler/lucene-solrlondonug-meetup28nov2014-solr-es-performance)
> - Hardware and master nodes heap :  
> [Redirecting to Google Groups](https://groups.google.com/forum/?fromgroups#!searchin/elasticsearch/sizing/elasticsearch/V5BtrCGOqoU/l7x6vqMEx5YJ)
> - _6th slide_ - Hardware and storage with number of documents (well,  
> without indexes and documents storage volume nor RAM consumption) :
> 
> [https://speakerdeck.com/bhaskarvk/scaling-elasticsearch-washington-dc-meetup](https://speakerdeck.com/bhaskarvk/scaling-elasticsearch-washington-dc-meetup)  
> With JBOD / SAN storage discussion in "To Raid or not to Raid":
> 
> [Redirecting to Google Groups](https://groups.google.com/forum/?fromgroups#!searchin/elasticsearch/hardware/elasticsearch/HSj2fZGdU1Y/4mFCBTCb-JcJ)
> 
> - Usual heap considerations in a real case :
> 
> [https://codeascraft.com/2014/12/04/juggling-multiple-elasticsearch-instances-on-a-single-host/](https://codeascraft.com/2014/12/04/juggling-multiple-elasticsearch-instances-on-a-single-host/)
> 
> Do not forget Elasticsearch awesome docs for moving to production  
> considerations :
> 
> - 
> 
> ## [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/administration.html)
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/deploy.html)
> 
> - _[Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/hardware.html)  
> [http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/hardware.html](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/hardware.html)_
> - _[Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/heap-sizing.html)  
> [http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/heap-sizing.html](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/heap-sizing.html)_
> 
> --  
> 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/927f60b1-8ae2-463e-b725-5f4f993905d9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/927f60b1-8ae2-463e-b725-5f4f993905d9%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/927f60b1-8ae2-463e-b725-5f4f993905d9%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/927f60b1-8ae2-463e-b725-5f4f993905d9%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/CAGe-ML%2B1EXPXxF6B1yr\_ubcOFTgAPJQFUwJjY2b-Ffigv1zr%3Dg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGe-ML%2B1EXPXxF6B1yr_ubcOFTgAPJQFUwJjY2b-Ffigv1zr%3Dg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![rondelvictor](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@rondelvictor](https://discuss.elastic.co/u/rondelvictor)\
**Post date:** [February 13, 2015, 6:02pm UTC](https://discuss.elastic.co/t/moving-to-production-considerations-applications-with-their-clusters-infrastructure/22136/3 "2015-02-13T18:02:24Z")

</div>

Hi Charlie,

That's excellent news! Thank you for your slideshare and related github!

Regards,

Victor

Le vendredi 13 février 2015 16:07:11 UTC+1, Charlie Hull a écrit :

> Hi,
> 
> Firstly, thanks for the kind words about the performance study: we're  
> hoping to revisit this soon after the feedback we've had on better tuning  
> for each engine. I agree there's a paucity of studies, but in a month or  
> two we should have one from a project we're working on to build an index of  
> product data - we hope to present this at the London Meetup group but will  
> publish the slides afterwards. Sorry this is in the future!
> 
> Cheers
> 
> Charlie
> 
> On 12 February 2015 at 14:27, \<[rondel...@gmail.com](mailto:rondel...@gmail.com) \<javascript:\>\> wrote:
> 
> > Hi everyone,
> > 
> > I am considering moving one or several elasticsearch clusters to  
> > production.  
> > Although Elasticsearch's documentation and community is _great_, I am  
> > strongly startled not to find any _complete use-case story_ stretching  
> > from application(s) needs and data considerations to hardware ones.  
> > Indeed, I understand why "what/how much hardware / configuration /  
> > sharding" questions are systematically replied with both "it depends"  
> > followed by "test".  
> > But then, what about a few complete descriptions, out of so many  
> > elasticsearch users, from data use case to cluster's internals, along with  
> > a few performance and nodes stats?
> > 
> > So here are questions, before moving to production :
> > 
> > Are there any _complete_ use cases around? Could you share some? By  
> > complete I mean including _at least some_ of the following :
> > 
> > 1. _Application needs and scope_
> > 2. _Indexing Data indications_ : data volume, documents mapping,  
> > documents / indexes volume
> > 3. _Searching Data indications_ : different applications, queries,  
> > use of facets - filters - aggregations, concurrent indexing
> > 4. _Cluster Hardware_ : machines' hardware (RAM, Disks/SSD -  
> > DAS-JBOD/SAN/NAS), JVM heap / OS Cache, nb of machines, back office network
> > 5. _Cluster Configuration_ : one or several indexes, sharding,  
> > replication, master nodes, data nodes, use of over-sharding at start-up,  
> > use of re-indexing
> > 6. \*Benchmaks \*: queries response times, QPS, with or without  
> > concurrent indexing, memory heap sweet spot, nodes stats
> > 
> > For those interested, here are the (not _complete_) best-among-very-few  
> > exemples I've stumbled upon so far :
> > 
> > - The very best (perfs with hardware and query description) :  
> > [Solr and Elasticsearch, a performance study | PPT](http://fr.slideshare.net/charliejuggler/lucene-solrlondonug-meetup28nov2014-solr-es-performance)
> > - Hardware and master nodes heap :  
> > [Redirecting to Google Groups](https://groups.google.com/forum/?fromgroups#!searchin/elasticsearch/sizing/elasticsearch/V5BtrCGOqoU/l7x6vqMEx5YJ)
> > - _6th slide_ - Hardware and storage with number of documents (well,  
> > without indexes and documents storage volume nor RAM consumption) :
> > 
> > [https://speakerdeck.com/bhaskarvk/scaling-elasticsearch-washington-dc-meetup](https://speakerdeck.com/bhaskarvk/scaling-elasticsearch-washington-dc-meetup)  
> > With JBOD / SAN storage discussion in "To Raid or not to Raid":
> > 
> > [Redirecting to Google Groups](https://groups.google.com/forum/?fromgroups#!searchin/elasticsearch/hardware/elasticsearch/HSj2fZGdU1Y/4mFCBTCb-JcJ)
> > 
> > - Usual heap considerations in a real case :
> > 
> > [https://codeascraft.com/2014/12/04/juggling-multiple-elasticsearch-instances-on-a-single-host/](https://codeascraft.com/2014/12/04/juggling-multiple-elasticsearch-instances-on-a-single-host/)
> > 
> > Do not forget Elasticsearch awesome docs for moving to production  
> > considerations :
> > 
> > - 
> > 
> > ## [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/administration.html)
> > 
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/deploy.html)
> > 
> > - _[Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/hardware.html)  
> > [http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/hardware.html](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/hardware.html)_
> > - _[Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/heap-sizing.html)  
> > [http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/heap-sizing.html](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/heap-sizing.html)_
> > 
> > --  
> > 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/927f60b1-8ae2-463e-b725-5f4f993905d9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/927f60b1-8ae2-463e-b725-5f4f993905d9%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/927f60b1-8ae2-463e-b725-5f4f993905d9%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/927f60b1-8ae2-463e-b725-5f4f993905d9%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/34acb9f4-a622-4ed6-b877-d605f0c6382b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/34acb9f4-a622-4ed6-b877-d605f0c6382b%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:32am UTC](https://discuss.elastic.co/t/moving-to-production-considerations-applications-with-their-clusters-infrastructure/22136/4 "2017-07-06T00:32:52Z")

</div>