Nathan: The page at https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html gives you good advice on a maximum size for the elasticsearch VM's memory.
Nathan: suggest you pick a flavor with 64GB RAM or less, then base other sizing things off of that (i.e. choose a flavor with 64GB of RAM and as many CPUs as possible for that RAM allocation, then base disk size on testing of your use case) Nathan: give java heap 30GB, and leave the rest of the memory to the OS filesystem cache so that Lucene can make best use of it. Nathan: that's mostly it for tuning. elasticsearch publishes many other docs for tuning recommendations, but there isn't anything specific to openstack besides the flavor choice. i personally chose CPU size (8CPU) such that all vCPUs for each VM would fit on a single NUMA node, which is a best practice for ESXi but not sure if it applies to KVM. (resending for clarity) On Fri, Sep 2, 2016 at 6:46 AM, David Medberry <openst...@medberry.net> wrote: > Hey Tim, > We've just started this effort. I'll see if the guy running the service > can comment today. > > On Fri, Sep 2, 2016 at 6:36 AM, Tim Bell <tim.b...@cern.ch> wrote: > >> >> >> Has anyone had experience running ElasticSearch on top of OpenStack VMs ? >> >> >> >> Are there any tuning recommendations ? >> >> >> >> Thanks >> >> Tim >> >> _______________________________________________ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
