# High CPU load

**URL:** <https://discuss.elastic.co/t/high-cpu-load/9262>\
**Category:** Elasticsearch\
**Created:** [October 7, 2012, 1:37am UTC](https://discuss.elastic.co/t/high-cpu-load/9262 "2012-10-07T01:37:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![courtenay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/courtenay/32/1933_2.png) [@courtenay](https://discuss.elastic.co/u/courtenay)\
**Post date:** [October 7, 2012, 1:37am UTC](https://discuss.elastic.co/t/high-cpu-load/9262/1 "2012-10-07T01:37:35Z")

</div>

Hey all, I'm seeing really high cpu load across most of my cluster (4  
m2.xlarge ec2 instances, 17gb ram). We also get timeouts on searching  
despite search and index volume being in the magnitude of 1-5 per second.

Here's a dump from jstack on one of the servers and our  
config: [https://gist.github.com/ba4bc5609f71ede28132](https://gist.github.com/ba4bc5609f71ede28132)

I only have 5m documents at a size 35GB. Many requests just time out - we  
turned on http logging with jetty and those requests just don't make it.

Any ideas for further debugging? Unfortunately I have no idea how to read a  
java stack.

-- Courtenay

--

---

<div class="post-metadata">

**Author:** ![drewr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drewr/32/7803_2.png) [@drewr](https://discuss.elastic.co/u/drewr)\
**Post date:** [October 9, 2012, 2:59pm UTC](https://discuss.elastic.co/t/high-cpu-load/9262/2 "2012-10-09T14:59:09Z")

</div>

courtenay wrote:

> Hey all, I'm seeing really high cpu load across most of my cluster  
> (4 m2.xlarge ec2 instances, 17gb ram). We also get timeouts on  
> searching despite search and index volume being in the magnitude of  
> 1-5 per second.
> 
> Here's a dump from jstack on one of the servers and our  
> config: [jstack · GitHub](https://gist.github.com/ba4bc5609f71ede28132)
> 
> I only have 5m documents at a size 35GB. Many requests just time  
> out - we turned on http logging with jetty and those requests just  
> don't make it.
> 
> Any ideas for further debugging? Unfortunately I have no idea how  
> to read a java stack.

The thread dump looks normal, although there could have been a few  
filesystem operations hanging. Are your indices stored on EBS?

Are you able to isolate what queries are taking so long? Can you  
post those or send them to me privately? Seems odd given your small  
dataset.

-Drew

--

---

<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 6, 2017, 3:09am UTC](https://discuss.elastic.co/t/high-cpu-load/9262/3 "2017-07-06T03:09:33Z")

</div>