# High CPU & Memory Usage

**URL:** https://discuss.elastic.co/t/high-cpu-memory-usage/36358
**Category:** Elasticsearch
**Created:** [December 4, 2015, 9:27am UTC](https://discuss.elastic.co/t/high-cpu-memory-usage/36358 "2015-12-04T09:27:53Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Astro-es](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@Astro-es](https://discuss.elastic.co/u/Astro-es)
#### Post date: [December 4, 2015, 9:27am UTC](https://discuss.elastic.co/t/high-cpu-memory-usage/36358/1 "2015-12-04T09:27:53Z")

</div>

Hi,

We have been facing high CPU and memory usage in ES cluster which fails to send logs to the dashboard.

Setup:  
ES cluster 2 nodes  
ES Version: 2.0.0  
No of total indices:13  
No of open indices: 3  
Total size of open indices: 28GB  
RAM:16GB Master  
No of replicas 1:  
No of shards:2

ES HEAP SIZE=8g  
bootstrap.mlockall: true  
indices.fielddata.cache.size: 20%

ES logs:

[2015-12-04 05:39:55,631][WARN][monitor.jvm] [elastic-node-1] [gc][young][565][1271] duration [2.3s], collections [1]/[2.6s], total [2.3s]/[3.1m], memory [5.9gb]-\>[6gb]/[7.9gb], all\_pools {[young] [123.9kb]-\>[4.1kb]/[133.1mb]}{[survivor] [16.6mb]-\>[16.6mb]/[16.6mb]}{[old] [5.9gb]-\>[6gb]/[7.8gb]}

Fluentd logs:

2015-12-04 08:31:31 +0000 [warn]: temporarily failed to flush the buffer. next\_retry=2015-12-04 09:34:07 +0000 error\_class="Fluent::ElasticsearchOutput::ConnectionFailure" error="Could not push logs to Elasticsearch after 2 retries. read timeout reached" plugin\_id="object:3f43554332e5c"

free -m  
total used free shared buffers cached  
Mem: 5298 14596 702 0 101 3265  
-/+ buffers/cache: 11229 4069  
Swap: 0 0 0

What may be the reason for this load? What is the recommended hardware configurations, elasticsearch configurations to make this normal?

---

<div class="post-metadata">

### 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: [December 5, 2015, 12:19am UTC](https://discuss.elastic.co/t/high-cpu-memory-usage/36358/2 "2015-12-05T00:19:24Z")

</div>

That's an awfully long GC.

What sort of data is it? Do you have Marvel installed?

---

<div class="post-metadata">

### Author: ![Astro-es](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@Astro-es](https://discuss.elastic.co/u/Astro-es)
#### Post date: [December 5, 2015, 10:36am UTC](https://discuss.elastic.co/t/high-cpu-memory-usage/36358/3 "2015-12-05T10:36:45Z")

</div>

We're storing logs from multiple servers to ES cluster.

Don't have Marvel Installed.

---

<div class="post-metadata">

### 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: [December 5, 2015, 10:02pm UTC](https://discuss.elastic.co/t/high-cpu-memory-usage/36358/4 "2015-12-05T22:02:56Z")

</div>

You should install Marvel so you can see what is happening.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:33pm UTC](https://discuss.elastic.co/t/high-cpu-memory-usage/36358/5 "2017-07-05T23:33:21Z")

</div>


