I've been using the elasticsearch rpms (1.1.1) on our centos 6.5 setup and
I've been wondering about the recommended way to configure it given that it
deploys an init.d script with defaults.
I figured out that I can use /etc/sysconfig/elasticsearch for things like
heap size. However, /usr/share/elasticsearch/bin/elasticsearch.in.sh
configures some defaults for garbage collection:
So, I'm getting some default configuration for garbage collection that I
probably should be tuning; especially given that it is running out of
memory after a few weeks on our setup with kibana and a rather large amount
of logstash indices (over 200GB).
Is it possible to have a custom garbage collection strategy without
modifying files deployed and overwritten by the rpm? elasticsearch.in.sh
seems specific to the 1.1.1 version given that it also includes the
In any case, it might be handy to clarify the recommended way to configure
elasticsearch when deployed using the rpm as opposed to a developer machine
with a tar ball. Most documentation I'm finding seems to assume the latter.
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 firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/182eb657-9503-42f6-8007-41150143fe46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.