# Optimizing configuration (Help me) **URL:** \ **Category:** Elasticsearch\ **Created:** [February 21, 2014, 12:20pm UTC](https://discuss.elastic.co/t/optimizing-configuration-help-me/15948 "2014-02-21T12:20:54Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![onthefloorr](https://avatars.discourse-cdn.com/v4/letter/o/ee7513/32.png) [@onthefloorr](https://discuss.elastic.co/u/onthefloorr)\ **Post date:** [February 21, 2014, 12:20pm UTC](https://discuss.elastic.co/t/optimizing-configuration-help-me/15948/1 "2014-02-21T12:20:54Z")
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 : cluster.name: essearchlocal thrift.port: 9500 index.cache.field.type: soft index.cache.field.max\_size: 20000 index.cache.field.expire: 25m index.refresh\_interval: 30s indices.fielddata.cache.size: 15% indices.fielddata.cache.expire: 6h indices.cache.filter.size: 15% indices.cache.filter.expire: 6h indices.memory.index\_buffer\_size: 70% indices.store.throttle.type: merge indices.store.throttle.max\_bytes\_per\_sec: 25mb indices.recovery.concurrent\_streams: 3 indices.recovery.max\_bytes\_per\_sec: 20mb index.translog.flush\_threshold\_ops: 25000 index.merge.policy.max\_merge\_size: 500mb index.store.compress.stored: true threadpool.search.type: fixed threadpool.search.size: 20 threadpool.search.queue\_size: 1000 threadpool.bulk.type: fixed threadpool.bulk.size: 20 threadpool.bulk.queue\_size: 1000 threadpool.index.type: fixed threadpool.index.size: 20 threadpool.index.queue\_size: 1000 index.store.type: mmapfs # cluster settings # 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 # cluster.routing.allocation.cluster\_concurrent\_rebalance: 2 * * * 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 quickly ? 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. indices.recovery.concurrent\_streams: 20 indices.recovery.max\_bytes\_per\_sec: 1500mb 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d286b4ca-0d84-4d1f-a123-d2628649ac10%40googlegroups.com](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](https://groups.google.com/groups/opt_out). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [February 23, 2014, 11:46pm UTC](https://discuss.elastic.co/t/optimizing-configuration-help-me/15948/2 "2014-02-23T23:46:16Z")
Sounds like you need more nodes, which isn't easy to work around. You can try increasing the RAM to 64GB and then assigning 32GB to ES, but above that and you start losing to GC. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 21 February 2014 23:20, onthefloorr [onthefloorr@gmail.com](mailto:onthefloorr@gmail.com) wrote: > 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 : > cluster.name: essearchlocal > > thrift.port: 9500 > > index.cache.field.type: soft > index.cache.field.max\_size: 20000 > index.cache.field.expire: 25m > index.refresh\_interval: 30s > indices.fielddata.cache.size: 15% > indices.fielddata.cache.expire: 6h > indices.cache.filter.size: 15% > indices.cache.filter.expire: 6h > indices.memory.index\_buffer\_size: 70% > > indices.store.throttle.type: merge > indices.store.throttle.max\_bytes\_per\_sec: 25mb > > indices.recovery.concurrent\_streams: 3 > indices.recovery.max\_bytes\_per\_sec: 20mb > index.translog.flush\_threshold\_ops: 25000 > > index.merge.policy.max\_merge\_size: 500mb > index.store.compress.stored: true > > threadpool.search.type: fixed > threadpool.search.size: 20 > threadpool.search.queue\_size: 1000 > > threadpool.bulk.type: fixed > threadpool.bulk.size: 20 > threadpool.bulk.queue\_size: 1000 > > threadpool.index.type: fixed > threadpool.index.size: 20 > threadpool.index.queue\_size: 1000 > index.store.type: mmapfs > > # cluster settings > > # 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 > > # cluster.routing.allocation.cluster\_concurrent\_rebalance: 2 > > * * * > > 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 > quickly ? > 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. > > indices.recovery.concurrent\_streams: 20 > indices.recovery.max\_bytes\_per\_sec: 1500mb > > 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/d286b4ca-0d84-4d1f-a123-d2628649ac10%40googlegroups.com](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](https://groups.google.com/groups/opt_out). -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624ZC0-UXw3x24F6q15%2BSRrc0yp8EVSd4F%3DW8VxuWtf4mNA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZC0-UXw3x24F6q15%2BSRrc0yp8EVSd4F%3DW8VxuWtf4mNA%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:48am UTC](https://discuss.elastic.co/t/optimizing-configuration-help-me/15948/3 "2017-07-06T01:48:00Z")
Closed on July 6, 2017, 1:48am UTC