# Stability issues due to documention flaw ElasticSearch **URL:** \ **Category:** Elasticsearch\ **Created:** [May 9, 2014, 11:26am UTC](https://discuss.elastic.co/t/stability-issues-due-to-documention-flaw-elasticsearch/17428 "2014-05-09T11:26:29Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Jasper\_Siero](https://avatars.discourse-cdn.com/v4/letter/j/48db29/32.png) [@Jasper\_Siero](https://discuss.elastic.co/u/Jasper_Siero)\ **Post date:** [May 9, 2014, 11:26am UTC](https://discuss.elastic.co/t/stability-issues-due-to-documention-flaw-elasticsearch/17428/1 "2014-05-09T11:26:29Z")
We are investigating stability issues we encounter in our ES cluster, and feel that the ES documentation is lacking important information on this topic. The mailing list seems to fill the gap with the "Document about recommended hardware specs & sharding/index strategy" [http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate](http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate)... The information in this conversation looks important (for example shards should not be bigger then the heap size and the heap size should be half of the total memory) but we haven’t found this information in the documentation. We have two questions: - Did we overlook this in the official documentation? - If the official documentation is lacking this important information, what should we do to make this taken care of? Information about our cluster: 4 node Elasticsearch cluster 6 indices in use Number of active shards 114 version 0.90.3 JVM: VM name: Java HotSpot(TM) 64-Bit Server VM VM vendor: Oracle Corporation VM version: 23.25-b01 Java version: 1.7.0\_25 OS: virtual machine CentOS 6.5 20 GB memory CPU: CPU vendor: Intel CPU model: Common KVM processor (2099 MHz) CPU total logical cores: 2 CPU cache: 4kb Cluster-wide storage size: 140 GB ---
**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:** [May 9, 2014, 11:34am UTC](https://discuss.elastic.co/t/stability-issues-due-to-documention-flaw-elasticsearch/17428/2 "2014-05-09T11:34:59Z")
Your link doesn't work ☹ However this sort of info is going to be in the ES (soon to be) book - > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 9 May 2014 21:26, Jasper Siero [jasper.siero@target-holding.nl](mailto:jasper.siero@target-holding.nl) wrote: > We are investigating stability issues we encounter in our ES cluster, and > feel that the ES documentation is lacking import information on this topic. > > The mailing list seems to fill the gap with the "Document about recommended > hardware specs & sharding/index strategy" > > [http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate](http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate). > .. > > The information in this conversation looks important (for example shards > should not be bigger then the heap size and the heap size shoud be half of > the total memory) but we haven’t found this information in the > documentation. We have two questions: > > - Did we overlook this in the official documentation? > - If the official documentation is lacking this important information, what > should we do to make this taken care of? > > Information about our cluster: > > 4 node Elasticsearch cluster > 6 indices in use > Number of active shards 114 > version 0.90.3 > > JVM: > VM name: Java HotSpot(TM) 64-Bit Server VM > VM vendor: Oracle Corporation > VM version: 23.25-b01 > Java version: 1.7.0\_25 > > OS: > virtual machine > CentOS 6.5 > 20 GB memory > > CPU: > CPU vendor: Intel > CPU model: Common KVM processor (2099 MHz) > CPU total logical cores: 2 > CPU cache: 4kb > > Cluster-wide storage size: 140 GB > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631.html](http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- > 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/1399634790470-4055631.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1399634790470-4055631.post%40n3.nabble.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/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jasper\_Siero](https://avatars.discourse-cdn.com/v4/letter/j/48db29/32.png) [@Jasper\_Siero](https://discuss.elastic.co/u/Jasper_Siero)\ **Post date:** [May 9, 2014, 11:45am UTC](https://discuss.elastic.co/t/stability-issues-due-to-documention-flaw-elasticsearch/17428/3 "2014-05-09T11:45:31Z")
The correct URL is: [http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strategy-td4039398.html](http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strategy-td4039398.html) The ES book would be really appreciated. Could you tell me when the release date is planned? Kind regards, Jasper Siero * * * Van: Mark Walkom [via ElasticSearch Users] [ml-node+s115913n4055632h82@n3.nabble.com] Verzonden: vrijdag 9 mei 2014 13:36 Aan: Jasper Siero Onderwerp: Re: Stability issues due to documention flaw ElasticSearch Your link doesn't work ☹ However this sort of info is going to be in the ES (soon to be) book - [http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/index.html](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/index.html) Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [hidden email]\ web: [www.campaignmonitor.com](http://www.campaignmonitor.com)[http://www.campaignmonitor.com](http://www.campaignmonitor.com) On 9 May 2014 21:26, Jasper Siero \<[hidden email]\\> wrote: We are investigating stability issues we encounter in our ES cluster, and feel that the ES documentation is lacking import information on this topic. The mailing list seems to fill the gap with the "Document about recommended hardware specs & sharding/index strategy" [http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate](http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate)... The information in this conversation looks important (for example shards should not be bigger then the heap size and the heap size shoud be half of the total memory) but we haven’t found this information in the documentation. We have two questions: - Did we overlook this in the official documentation? - If the official documentation is lacking this important information, what should we do to make this taken care of? Information about our cluster: 4 node Elasticsearch cluster 6 indices in use Number of active shards 114 version 0.90.3 JVM: VM name: Java HotSpot(TM) 64-Bit Server VM VM vendor: Oracle Corporation VM version: 23.25-b01 Java version: 1.7.0\_25 OS: virtual machine CentOS 6.5 20 GB memory CPU: CPU vendor: Intel CPU model: Common KVM processor (2099 MHz) CPU total logical cores: 2 CPU cache: 4kb Cluster-wide storage size: 140 GB -- View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631.html](http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631.html) Sent from the ElasticSearch Users mailing list archive at [Nabble.com](http://Nabble.com). -- 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 [hidden email]\. To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1399634790470-4055631.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1399634790470-4055631.post%40n3.nabble.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 [hidden email]\. To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com)[https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com?utm_medium=email&utm_source=footer). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). * * * If you reply to this email, your message will be added to the discussion below: [http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631p4055632.html](http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631p4055632.html) To unsubscribe from Stability issues due to documention flaw ElasticSearch, click here[http://elasticsearch-users.115913.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe\_by\_code&node=4055631&code=amFzcGVyLnNpZXJvQHRhcmdldC1ob2xkaW5nLm5sfDQwNTU2MzF8OTA3NjMyNTM2](http://elasticsearch-users.115913.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4055631&code=amFzcGVyLnNpZXJvQHRhcmdldC1ob2xkaW5nLm5sfDQwNTU2MzF8OTA3NjMyNTM2). NAML[http://elasticsearch-users.115913.n3.nabble.com/template/NamlServlet.jtp?macro=macro\_viewer&id=instant\_html!nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify\_subscribers!nabble%3Aemail.naml-instant\_emails!nabble%3Aemail.naml-send\_instant\_email!nabble%3Aemail.naml](http://elasticsearch-users.115913.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml) ---
**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:** [May 9, 2014, 12:03pm UTC](https://discuss.elastic.co/t/stability-issues-due-to-documention-flaw-elasticsearch/17428/4 "2014-05-09T12:03:27Z")
Well O'Reilly has it as March 2014, I'm guessing that is not the fully edited version - [Elasticsearch: The Definitive Guide [Book]](http://shop.oreilly.com/product/0636920028505.do) Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 9 May 2014 21:46, Jasper Siero [jasper.siero@target-holding.nl](mailto:jasper.siero@target-holding.nl) wrote: > The correct URL is: > > [http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strategy-td4039398.html](http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strategy-td4039398.html) > > The ES book would be really appreciated. Could you tell me when the > release date is planned? > > Kind regards, > > Jasper Siero > > * * * > > _Van:_ Mark Walkom [via Elasticsearch Users] [ml-node+[hidden email][http://user/SendEmail.jtp?type=node&node=4055633&i=0](http://user/SendEmail.jtp?type=node&node=4055633&i=0) > ] > _Verzonden:_ vrijdag 9 mei 2014 13:36 > _Aan:_ Jasper Siero > _Onderwerp:_ Re: Stability issues due to documention flaw Elasticsearch > > Your link doesn't work ☹ > > However this sort of info is going to be in the ES (soon to be) book - > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/index.html) > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [hidden email] [http://UrlBlockedError.aspx](http://UrlBlockedError.aspx) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 9 May 2014 21:26, Jasper Siero \<[hidden email][http://UrlBlockedError.aspx](http://UrlBlockedError.aspx) > > > wrote: > > > We are investigating stability issues we encounter in our ES cluster, and > > feel that the ES documentation is lacking import information on this > > topic. > > > > The mailing list seems to fill the gap with the "Document about > > recommended > > hardware specs & sharding/index strategy" > > > > [http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate](http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate). > > .. > > > > The information in this conversation looks important (for example shards > > should not be bigger then the heap size and the heap size shoud be half of > > the total memory) but we haven’t found this information in the > > documentation. We have two questions: > > > > - Did we overlook this in the official documentation? > > - If the official documentation is lacking this important information, > > what > > should we do to make this taken care of? > > > > Information about our cluster: > > > > 4 node Elasticsearch cluster > > 6 indices in use > > Number of active shards 114 > > version 0.90.3 > > > > JVM: > > VM name: Java HotSpot(TM) 64-Bit Server VM > > VM vendor: Oracle Corporation > > VM version: 23.25-b01 > > Java version: 1.7.0\_25 > > > > OS: > > virtual machine > > CentOS 6.5 > > 20 GB memory > > > > CPU: > > CPU vendor: Intel > > CPU model: Common KVM processor (2099 MHz) > > CPU total logical cores: 2 > > CPU cache: 4kb > > > > Cluster-wide storage size: 140 GB > > > > -- > > View this message in context: > > [http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631.html](http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631.html) > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > > > -- > > 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 [hidden email] [http://UrlBlockedError.aspx](http://UrlBlockedError.aspx). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/1399634790470-4055631.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1399634790470-4055631.post%40n3.nabble.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 [hidden email] [http://UrlBlockedError.aspx](http://UrlBlockedError.aspx). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com)[https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > * * * > > If you reply to this email, your message will be added to the discussion > below: > > [http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631p4055632.html](http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631p4055632.html) > To unsubscribe from Stability issues due to documention flaw > Elasticsearch, click here. > NAML[http://elasticsearch-users.115913.n3.nabble.com/template/NamlServlet.jtp?macro=macro\_viewer&id=instant\_html!nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify\_subscribers!nabble%3Aemail.naml-instant\_emails!nabble%3Aemail.naml-send\_instant\_email!nabble%3Aemail.naml](http://elasticsearch-users.115913.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml) > > * * * > > View this message in context: RE: Stability issues due to documention > flaw Elasticsearch[http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631p4055633.html](http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631p4055633.html) > Sent from the Elasticsearch Users mailing list archive[http://elasticsearch-users.115913.n3.nabble.com/](http://elasticsearch-users.115913.n3.nabble.com/)at [Nabble.com](http://Nabble.com). > > -- > 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/865DC909675A2E40933A72B094A926EA2F5D691D%40mbx5.hosted.exchange-login.net](https://groups.google.com/d/msgid/elasticsearch/865DC909675A2E40933A72B094A926EA2F5D691D%40mbx5.hosted.exchange-login.net)[https://groups.google.com/d/msgid/elasticsearch/865DC909675A2E40933A72B094A926EA2F5D691D%40mbx5.hosted.exchange-login.net?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/865DC909675A2E40933A72B094A926EA2F5D691D%40mbx5.hosted.exchange-login.net?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/CAEM624bihEH1ugh6aL4BDFcCsRBvXkm08-ZT5qDuYVEPjkRdOg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624bihEH1ugh6aL4BDFcCsRBvXkm08-ZT5qDuYVEPjkRdOg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [May 9, 2014, 12:19pm UTC](https://discuss.elastic.co/t/stability-issues-due-to-documention-flaw-elasticsearch/17428/5 "2014-05-09T12:19:12Z")
Because each Elasticsearch workload and hardware plus software is different, you should not expect a serious documentation can always give "one-size-fits-all" advisory. There are many "rules of thumb" and best practices, mostly based on individual experience on individual test cases. The foundation may change in the future, because of other Java version, because of other hardware specs, or on other Elasticsearch versions etc. For example, "shards should not be bigger than the heap size" - this might be useful in situations where massive indexing is going on for that shard so that segment merging can proceed smoothly, or when you must recover from broken shards. Beside this, it is also not wrong to have huge shards. If you have a finalized index, never recover from replica, or never have to move a shard around, you will not even notice how large your shards are. It always depends on your requirements. Jörg On Fri, May 9, 2014 at 1:26 PM, Jasper Siero \ wrote: > We are investigating stability issues we encounter in our ES cluster, and > feel that the ES documentation is lacking import information on this topic. > > The mailing list seems to fill the gap with the "Document about recommended > hardware specs & sharding/index strategy" > > [http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate](http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate). > .. > > The information in this conversation looks important (for example shards > should not be bigger then the heap size and the heap size shoud be half of > the total memory) but we haven’t found this information in the > documentation. We have two questions: > > - Did we overlook this in the official documentation? > - If the official documentation is lacking this important information, what > should we do to make this taken care of? > > Information about our cluster: > > 4 node Elasticsearch cluster > 6 indices in use > Number of active shards 114 > version 0.90.3 > > JVM: > VM name: Java HotSpot(TM) 64-Bit Server VM > VM vendor: Oracle Corporation > VM version: 23.25-b01 > Java version: 1.7.0\_25 > > OS: > virtual machine > CentOS 6.5 > 20 GB memory > > CPU: > CPU vendor: Intel > CPU model: Common KVM processor (2099 MHz) > CPU total logical cores: 2 > CPU cache: 4kb > > Cluster-wide storage size: 140 GB > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631.html](http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- > 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/1399634790470-4055631.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1399634790470-4055631.post%40n3.nabble.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/CAKdsXoGVpWdYuhCD%3DzVoTEJEPxXq-zG8ViFHmm\_Qr%3DdAMVJccA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGVpWdYuhCD%3DzVoTEJEPxXq-zG8ViFHmm_Qr%3DdAMVJccA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Paige\_Cook](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paige_cook/32/1561_2.png) [@Paige\_Cook](https://discuss.elastic.co/u/Paige_Cook)\ **Post date:** [May 9, 2014, 12:20pm UTC](https://discuss.elastic.co/t/stability-issues-due-to-documention-flaw-elasticsearch/17428/6 "2014-05-09T12:20:24Z")
Here is a post from the Elasticsearch Blog that gives some more context and status of the book - elasticsearch – the definitive guide[http://www.elasticsearch.org/blog/elasticsearch-definitive-guide/](http://www.elasticsearch.org/blog/elasticsearch-definitive-guide/) On Friday, May 9, 2014 8:03:27 AM UTC-4, Mark Walkom wrote: > Well O'Reilly has it as March 2014, I'm guessing that is not the fully > edited version - [Elasticsearch: The Definitive Guide [Book]](http://shop.oreilly.com/product/0636920028505.do)[http://www.google.com/url?q=http%3A%2F%2Fshop.oreilly.com%2Fproduct%2F0636920028505.do&sa=D&sntz=1&usg=AFQjCNHsbG4AB7XXp9MeYfcDgeUKkEfpRw](http://www.google.com/url?q=http%3A%2F%2Fshop.oreilly.com%2Fproduct%2F0636920028505.do&sa=D&sntz=1&usg=AFQjCNHsbG4AB7XXp9MeYfcDgeUKkEfpRw) > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \ > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 9 May 2014 21:46, Jasper Siero \ > > > wrote: > > > The correct URL is: > > > > [http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strategy-td4039398.html](http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strategy-td4039398.html) > > > > The ES book would be really appreciated. Could you tell me when the > > release date is planned? > > > > Kind regards, > > > > Jasper Siero > > > > * * * > > > > _Van:_ Mark Walkom [via Elasticsearch Users] [ml-node+[hidden email][http://user/SendEmail.jtp?type=node&node=4055633&i=0](http://user/SendEmail.jtp?type=node&node=4055633&i=0) > > ] > > _Verzonden:_ vrijdag 9 mei 2014 13:36 > > _Aan:_ Jasper Siero > > _Onderwerp:_ Re: Stability issues due to documention flaw Elasticsearch > > > > Your link doesn't work ☹ > > > > However this sort of info is going to be in the ES (soon to be) book - > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/index.html) > > > > Regards, > > Mark Walkom > > > > Infrastructure Engineer > > Campaign Monitor > > email: [hidden email] [http://UrlBlockedError.aspx](http://UrlBlockedError.aspx) > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > On 9 May 2014 21:26, Jasper Siero \<[hidden email][http://UrlBlockedError.aspx](http://UrlBlockedError.aspx) > > > > > wrote: > > > > > We are investigating stability issues we encounter in our ES cluster, and > > > feel that the ES documentation is lacking import information on this > > > topic. > > > > > > The mailing list seems to fill the gap with the "Document about > > > recommended > > > hardware specs & sharding/index strategy" > > > > > > [http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate](http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate). > > > .. > > > > > > The information in this conversation looks important (for example shards > > > should not be bigger then the heap size and the heap size shoud be half > > > of > > > the total memory) but we haven’t found this information in the > > > documentation. We have two questions: > > > > > > - Did we overlook this in the official documentation? > > > - If the official documentation is lacking this important information, > > > what > > > should we do to make this taken care of? > > > > > > Information about our cluster: > > > > > > 4 node Elasticsearch cluster > > > 6 indices in use > > > Number of active shards 114 > > > version 0.90.3 > > > > > > JVM: > > > VM name: Java HotSpot(TM) 64-Bit Server VM > > > VM vendor: Oracle Corporation > > > VM version: 23.25-b01 > > > Java version: 1.7.0\_25 > > > > > > OS: > > > virtual machine > > > CentOS 6.5 > > > 20 GB memory > > > > > > CPU: > > > CPU vendor: Intel > > > CPU model: Common KVM processor (2099 MHz) > > > CPU total logical cores: 2 > > > CPU cache: 4kb > > > > > > Cluster-wide storage size: 140 GB > > > > > > -- > > > View this message in context: > > > [http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631.html](http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631.html) > > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > > > > > -- > > > 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 [hidden email] [http://UrlBlockedError.aspx](http://UrlBlockedError.aspx). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/1399634790470-4055631.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1399634790470-4055631.post%40n3.nabble.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 [hidden email] [http://UrlBlockedError.aspx](http://UrlBlockedError.aspx). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com)[https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZXWHXiaLu1QsAYzwX3oqwYywAsVbg2NnVPig9NKevSyQ%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > * * * > > > > If you reply to this email, your message will be added to the > > discussion below: > > > > [http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631p4055632.html](http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631p4055632.html) > > To unsubscribe from Stability issues due to documention flaw > > Elasticsearch, click here. > > NAML[http://elasticsearch-users.115913.n3.nabble.com/template/NamlServlet.jtp?macro=macro\_viewer&id=instant\_html!nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify\_subscribers!nabble%3Aemail.naml-instant\_emails!nabble%3Aemail.naml-send\_instant\_email!nabble%3Aemail.naml](http://elasticsearch-users.115913.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml) > > > > * * * > > > > View this message in context: RE: Stability issues due to documention > > flaw Elasticsearch[http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631p4055633.html](http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631p4055633.html) > > Sent from the Elasticsearch Users mailing list archive[http://elasticsearch-users.115913.n3.nabble.com/](http://elasticsearch-users.115913.n3.nabble.com/)at [Nabble.com](http://Nabble.com). > > > > -- > > 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/865DC909675A2E40933A72B094A926EA2F5D691D%40mbx5.hosted.exchange-login.net](https://groups.google.com/d/msgid/elasticsearch/865DC909675A2E40933A72B094A926EA2F5D691D%40mbx5.hosted.exchange-login.net)[https://groups.google.com/d/msgid/elasticsearch/865DC909675A2E40933A72B094A926EA2F5D691D%40mbx5.hosted.exchange-login.net?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/865DC909675A2E40933A72B094A926EA2F5D691D%40mbx5.hosted.exchange-login.net?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/3e77eb72-3890-45b1-a8b4-d7736aa64eff%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3e77eb72-3890-45b1-a8b4-d7736aa64eff%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:** [May 9, 2014, 12:25pm UTC](https://discuss.elastic.co/t/stability-issues-due-to-documention-flaw-elasticsearch/17428/7 "2014-05-09T12:25:17Z")
To add to this, you're still on 0.90.X and you should really upgrade as you will get the benefit of multiple fixes and updates. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 9 May 2014 22:19, [joergprante@gmail.com](mailto:joergprante@gmail.com) [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > Because each Elasticsearch workload and hardware plus software is > different, you should not expect a serious documentation can always give > "one-size-fits-all" advisory. There are many "rules of thumb" and best > practices, mostly based on individual experience on individual test cases. > The foundation may change in the future, because of other Java version, > because of other hardware specs, or on other Elasticsearch versions etc. > > For example, "shards should not be bigger than the heap size" - this might > be useful in situations where massive indexing is going on for that shard > so that segment merging can proceed smoothly, or when you must recover from > broken shards. Beside this, it is also not wrong to have huge shards. If > you have a finalized index, never recover from replica, or never have to > move a shard around, you will not even notice how large your shards are. It > always depends on your requirements. > > Jörg > > On Fri, May 9, 2014 at 1:26 PM, Jasper Siero \< > jasper.siero@target-holding.nl\> wrote: > > > We are investigating stability issues we encounter in our ES cluster, and > > feel that the ES documentation is lacking import information on this > > topic. > > > > The mailing list seems to fill the gap with the "Document about > > recommended > > hardware specs & sharding/index strategy" > > > > [http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate](http://elasticsearch-users.115913.n3.nabble.com/Recommended-Hardware-Specs-amp-Sharding-Index-Strate). > > .. > > > > The information in this conversation looks important (for example shards > > should not be bigger then the heap size and the heap size shoud be half of > > the total memory) but we haven’t found this information in the > > documentation. We have two questions: > > > > - Did we overlook this in the official documentation? > > - If the official documentation is lacking this important information, > > what > > should we do to make this taken care of? > > > > Information about our cluster: > > > > 4 node Elasticsearch cluster > > 6 indices in use > > Number of active shards 114 > > version 0.90.3 > > > > JVM: > > VM name: Java HotSpot(TM) 64-Bit Server VM > > VM vendor: Oracle Corporation > > VM version: 23.25-b01 > > Java version: 1.7.0\_25 > > > > OS: > > virtual machine > > CentOS 6.5 > > 20 GB memory > > > > CPU: > > CPU vendor: Intel > > CPU model: Common KVM processor (2099 MHz) > > CPU total logical cores: 2 > > CPU cache: 4kb > > > > Cluster-wide storage size: 140 GB > > > > -- > > View this message in context: > > [http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631.html](http://elasticsearch-users.115913.n3.nabble.com/Stability-issues-due-to-documention-flaw-ElasticSearch-tp4055631.html) > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > > > -- > > 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/1399634790470-4055631.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1399634790470-4055631.post%40n3.nabble.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/CAKdsXoGVpWdYuhCD%3DzVoTEJEPxXq-zG8ViFHmm\_Qr%3DdAMVJccA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGVpWdYuhCD%3DzVoTEJEPxXq-zG8ViFHmm_Qr%3DdAMVJccA%40mail.gmail.com)[https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGVpWdYuhCD%3DzVoTEJEPxXq-zG8ViFHmm\_Qr%3DdAMVJccA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGVpWdYuhCD%3DzVoTEJEPxXq-zG8ViFHmm_Qr%3DdAMVJccA%40mail.gmail.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/CAEM624aWi\_vQhW4ZbXNoUsx3skMnFpO6MsLJFR4Q%2BJOymeMNdg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624aWi_vQhW4ZbXNoUsx3skMnFpO6MsLJFR4Q%2BJOymeMNdg%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, 1:30am UTC](https://discuss.elastic.co/t/stability-issues-due-to-documention-flaw-elasticsearch/17428/8 "2017-07-06T01:30:33Z")