Hi, I would like to ask for your help with the following :
I have two servers on which the elasticsearch is already installed and they
are configured with the following :
index.merge.policy.max_merged_segment: 1gb # it hasn't been tested yet
indices.fielddata.cache.size: 10% # it hasn't been tested yet
multicast.enabled: false # it hasn't been tested yet
discovery.zen.ping_timeout: 5s # it hasn't been tested yet
discovery.zen.minimum_master_nodes: 2 # it hasn't been tested yet
discovery.zen.ping.unicast.hosts: [""] # it hasn't been tested yet
Each server has 24GB of physical memory available, but we are running
elasticsearch in a standalone mode.
There are two applications that insert logs into Elasticsearch at the same
time, and 16Gb of memory is added to Elasticsearch for handling requests.
There are 8 GB of memory available for the system.
So our problem is, when a search is started the load avarage of the system
will be 'too high', and the system
will be unusable, and sometimes we will get SearchRequest Exception
(java.lang.outofmemoryerror java heap space) .
Could you suggest me a better configuration for solve these problems ?
We can't provide more server for Elasticsearch and we can run only it on
one node, so we can't run it in cluster mode.
Are the problems solved, if we put more memory into the server on where the
Elasticsearch is running ?
I also wanted to ask how can I make the elasticsearch to recover itself
We have 150 index ( 750 shard ) , and each index size is about 20 GB.
I tried to give high values to recovery options, but it hasn't effect.
Our servers configuration :
- Intel(R) Xeon(R) CPU E5345 @ 2.33Ghz (8 core)
- 24 GB memory DDR2
- 4 TB SSHD ( Hybrid )
(Elasticsearch version : 0.90.10)
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/d286b4ca-0d84-4d1f-a123-d2628649ac10%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.