Open Stack

omitted on more line:

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.

On Fri, Sep 2, 2016 at 2:15 PM, David Medberry <openstack at medberry.net>
wrote:

> From Nathan (on TWC Cloud team):
>
> 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)
>
> On Fri, Sep 2, 2016 at 6:46 AM, David Medberry <openstack at 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.Bell at 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 at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160902/00e2c2b3/attachment.html>