Hello,
I'm not aware of existing documents that will help you on this specific
field. And I think the reason for that is because there are many variables.
Regarding sizing your nodes, the way you're using Elasticsearch matters a
lot. For example, if you stress it more on indexing than on searching,
you'll probably need more CPU than RAM. If indexing is light, and indices
fit in the OS caches, the I/O speed wouldn't matter that much. On the other
hand, if your indices are large and ES goes to disk often, I/O would be the
bottleneck and it might be worth getting SSDs.
Regarding scaling, the easiest way to go at it is by adding nodes. If you
want more concurrent searches, it's probably better to increase the number
of replicas with the number of nodes. If you can have bigger nodes, you'll
probably be better of with some of those, than with many small nodes.
I think it's best to describe your setup in more details (ie: where you are
and where you want to be), and you'll get advice that will suit your needs.
Best regards,
Radu
http://sematext.com/ -- Elasticsearch -- Solr -- Lucene
On Fri, May 3, 2013 at 5:15 PM, Kubes philip@freepricealerts.com wrote:
Hello,
We have been running Elasticsearch for several months and are now
expanding its use. I am looking for guides / best practices for sizing
(CPU/RAM) and scaling the nodes, number of nodes, etc. Are there
any documents to assist on this planning?
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.