We deployed elasticsearch on 3 nodes and assign 12GB heap to elasticsearch
process. But as the data increasing, the elasticsearch became slower.
There are 670 indices. We are going to keep 2 years data. Each date is an
index. Now, an index may have 10w+ documents at the most.
*Here is the cluster's status:*
curl 'localhost:9200/_cat/fielddata?v'
id node
total geolocation data.created_at domain media
noun_phrases
-r1BLlrlRem5xhNPTni3zQ Overmind 2gb
75mb 17.9mb 40.5mb 68mb 1.8gb
BbPoFxvSRMONo_U4aVEd0A Cordelia Frost 4gb 104.2mb
29.8mb 145.2mb 104.2mb 3.6gb
2hGuYqK-RIO4pw1qZVJQFQ Jack-in-the-Box 3.4gb 87mb
25.2mb 78mb 86.4mb 3.1gb
*the jvm parameter is as follow*:
org.elasticsearch.bootstrap.Elasticsearch -Xms12g -Xmx12g -Xss256k
-Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly
-XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.foreground=yes
-Des.path.home=/opt/elasticsearch-1.2.1
So, my question is how can we improve it? Add more machines? If we add
machines, how can we estimate how many machines we need? Is there possible
to improve just for these 3 machines?
--
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/4875f12f-af0c-4531-b109-6ff5140a971e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
