# ES suddenly begin to consume CPU

**URL:** <https://discuss.elastic.co/t/es-suddenly-begin-to-consume-cpu/29416>\
**Category:** Elasticsearch\
**Created:** [September 16, 2015, 2:47pm UTC](https://discuss.elastic.co/t/es-suddenly-begin-to-consume-cpu/29416 "2015-09-16T14:47:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![shakura](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@shakura](https://discuss.elastic.co/u/shakura)\
**Post date:** [September 16, 2015, 2:47pm UTC](https://discuss.elastic.co/t/es-suddenly-begin-to-consume-cpu/29416/1 "2015-09-16T14:47:57Z")

</div>

Hi!  
I have 6-nodes cluster. Sometimes cpu usage become very high and lows only after restarting elastic.  
Any suggestions?

Here is my munin output:

 ![](https://us1.discourse-cdn.com/elastic/original/2X/a/a3f66c53a025f3e341607e4dedbdd50789076772.png)  
And hot threads from one of the nodes:

* * *

Hot threads at 2015-09-16T14:30:20.501Z, interval=500ms, busiestThreads=3, ignoreIdleThreads=true:

18.7% (93.3ms out of 500ms) cpu usage by thread 'elasticsearch[br-es-03][search][T#3]'  
4/10 snapshots sharing following 20 elements  
org.apache.lucene.search.ConstantScoreQuery$ConstantScorer.nextDoc(ConstantScoreQuery.java:257)  
org.apache.lucene.search.Weight$DefaultBulkScorer.scoreAll(Weight.java:192)  
org.apache.lucene.search.Weight$DefaultBulkScorer.score(Weight.java:163)  
org.apache.lucene.search.BulkScorer.score(BulkScorer.java:35)  
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:621)  
org.elasticsearch.search.internal.ContextIndexSearcher.search(ContextIndexSearcher.java:191)  
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:491)  
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:448)  
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:281)  
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:269)  
org.elasticsearch.search.query.QueryPhase.execute(QueryPhase.java:157)  
org.elasticsearch.search.SearchService.loadOrExecuteQueryPhase(SearchService.java:286)  
org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:297)  
org.elasticsearch.search.action.SearchServiceTransportAction$SearchQueryTransportHandler.messageReceived(SearchServiceTransportAction.java:776)  
org.elasticsearch.search.action.SearchServiceTransportAction$SearchQueryTransportHandler.messageReceived(SearchServiceTransportAction.java:767)  
org.elasticsearch.transport.netty.MessageChannelHandler$RequestHandler.doRun(MessageChannelHandler.java:277)  
org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:36)  
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
java.lang.Thread.run(Thread.java:722)  
6/10 snapshots sharing following 10 elements  
sun.misc.Unsafe.park(Native Method)  
java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)  
java.util.concurrent.LinkedTransferQueue.awaitMatch(LinkedTransferQueue.java:735)  
java.util.concurrent.LinkedTransferQueue.xfer(LinkedTransferQueue.java:644)  
java.util.concurrent.LinkedTransferQueue.take(LinkedTransferQueue.java:1137)  
org.elasticsearch.common.util.concurrent.SizeBlockingQueue.take(SizeBlockingQueue.java:162)  
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)  
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)  
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
java.lang.Thread.run(Thread.java:722)

---

<div class="post-metadata">

**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\
**Post date:** [September 17, 2015, 5:45pm UTC](https://discuss.elastic.co/t/es-suddenly-begin-to-consume-cpu/29416/2 "2015-09-17T17:45:37Z")

</div>

Hi,

Can you share more than just your CPU metrics?  
Is GC high?  
How about query rates?  
What about merges and disk IO?  
Jump in evictions or size of your Threadpool queues?  
...

## Otis

Monitoring \* Alerting \* Anomaly Detection \* Centralized Log Management  
Elasticsearch Consulting & Support \* [http://sematext.com/](http://sematext.com/)

---

<div class="post-metadata">

**Author:** ![shakura](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@shakura](https://discuss.elastic.co/u/shakura)\
**Post date:** [September 23, 2015, 8:10am UTC](https://discuss.elastic.co/t/es-suddenly-begin-to-consume-cpu/29416/3 "2015-09-23T08:10:56Z")

</div>

Hi, the problem was the error in client application. It tried to update large bulks of non-existent documents.

---

<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:48pm UTC](https://discuss.elastic.co/t/es-suddenly-begin-to-consume-cpu/29416/4 "2017-07-05T23:48:32Z")

</div>