Hi Jilles,

Any idea on why you're running out of memory? You can monitor stuff like
field, filter caches and memory pools to get some clues.

I would assume your problem is because field data is accumulating, and not
because of GC settings. Depending on how much heap, how many nodes you
have, and how much heap is used for other things, I'd limit that a slice of
the total memory (for example, 30%).

Best regards,
Radu
--
Performance Monitoring * Log Analytics * Search Analytics
Solr & Elasticsearch Support * http://sematext.com/


On Fri, Apr 25, 2014 at 7:09 PM, Jilles van Gurp <[email protected]>wrote:

> 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.shconfigures some defaults for 
> garbage collection:
>
> JAVA_OPTS="$JAVA_OPTS -XX:+UseParNewGC"
> JAVA_OPTS="$JAVA_OPTS -XX:+UseConcMarkSweepGC"
>
> JAVA_OPTS="$JAVA_OPTS -XX:CMSInitiatingOccupancyFraction=75"
> JAVA_OPTS="$JAVA_OPTS -XX:+UseCMSInitiatingOccupancyOnly"
>
> 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.shseems 
> specific to the 1.1.1 version given that it also includes the
> classpath definition.
>
> 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.
>
> Jilles
>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/182eb657-9503-42f6-8007-41150143fe46%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/182eb657-9503-42f6-8007-41150143fe46%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAHXA0_0h10irKcsRU%3DPDu5DrVPACnSq01sZestFYrwftqze%3DAg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to