# 100% peak of processing in one of the machines **URL:** \ **Category:** Elasticsearch\ **Created:** [March 1, 2017, 2:09pm UTC](https://discuss.elastic.co/t/100-peak-of-processing-in-one-of-the-machines/76992 "2017-03-01T14:09:36Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![RafaelPosthaus](https://avatars.discourse-cdn.com/v4/letter/r/73ab20/32.png) [@RafaelPosthaus](https://discuss.elastic.co/u/RafaelPosthaus)\ **Post date:** [March 1, 2017, 2:09pm UTC](https://discuss.elastic.co/t/100-peak-of-processing-in-one-of-the-machines/76992/1 "2017-03-01T14:09:36Z")
Good morning, how are you? I'm a friend of Waldemar Neto, and I work with elastic from V1.2, Today I released production on v2.4.2, but I noticed that every 5 minutes I have a 100% peak of processing in one of the machines, nothing that affects the performance, but can you give me a tip, a way I can Have configured, to occur this peak? Our bases are small, 23,000 documents, a total size of 130 mb, my settings are: index.refresh\_interval: 30s index.requests.cache.enable": true indices.requests.cache.size: 4% indices.queries.cache.size: 20% indices.breaker.total.limit: 85% indices.fielddata.cache.size: 20% ---
**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\ **Post date:** [March 1, 2017, 2:23pm UTC](https://discuss.elastic.co/t/100-peak-of-processing-in-one-of-the-machines/76992/2 "2017-03-01T14:23:12Z")
Hello Rafael, you could use hot\_thread API to see whats going on: [https://www.elastic.co/guide/en/elasticsearch/reference/2.4/cluster-nodes-hot-threads.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/cluster-nodes-hot-threads.html) Is your elasticsearch is alone on this machine ? Whats the hardwarde config. ? ---
**Author:** ![RafaelPosthaus](https://avatars.discourse-cdn.com/v4/letter/r/73ab20/32.png) [@RafaelPosthaus](https://discuss.elastic.co/u/RafaelPosthaus)\ **Post date:** [March 1, 2017, 2:42pm UTC](https://discuss.elastic.co/t/100-peak-of-processing-in-one-of-the-machines/76992/3 "2017-03-01T14:42:19Z")
Yes I have only the elastic in each machine, it follows the standard configurations. Intel (R) Xeon (R) CPU E5-2630 v3 @ 2.40GHz, 8 colors, 20Gb Ram this is result of hot-trheads: ::: {esprodnovo1}{ktcu\_LCcRNedF70aEXDF5A}{192.168.1.77}{192.168.1.77:9300} Hot threads at 2017-03-01T14:42:31.582Z, interval=500ms, busiestThreads=3, ignoreIdleThreads=true: ::: {esprodnovo2}{B1K9hzbPRrSGD7ZjT4xgSA}{192.168.1.78}{192.168.1.78:9300} Hot threads at 2017-03-01T14:41:25.017Z, interval=500ms, busiestThreads=3, ignoreIdleThreads=true: ``` 2.2% (10.7ms out of 500ms) cpu usage by thread 'elasticsearch[esprodnovo2][transport_client_worker][T#7]{New I/O worker #7}' 2/10 snapshots sharing following 15 elements org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) java.lang.Thread.run(Thread.java:745) 2.1% (10.7ms out of 500ms) cpu usage by thread 'elasticsearch[esprodnovo2][transport_client_worker][T#8]{New I/O worker #8}' 3/10 snapshots sharing following 7 elements org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) java.lang.Thread.run(Thread.java:745) ``` ---
**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\ **Post date:** [March 2, 2017, 2:44pm UTC](https://discuss.elastic.co/t/100-peak-of-processing-in-one-of-the-machines/76992/4 "2017-03-02T14:44:22Z")
Can you get hot\_thread when you see CPU pikes? ---
**Author:** ![RafaelPosthaus](https://avatars.discourse-cdn.com/v4/letter/r/73ab20/32.png) [@RafaelPosthaus](https://discuss.elastic.co/u/RafaelPosthaus)\ **Post date:** [March 2, 2017, 3:26pm UTC](https://discuss.elastic.co/t/100-peak-of-processing-in-one-of-the-machines/76992/5 "2017-03-02T15:26:35Z")
The peaks are very fast, it is difficult to get at the exact moment, you tell me where I get a good practical example in java to solve this problem? QueryPhaseExecutionException [Result window is too large, from + size must be less than or equal to: [999999999] but was [1410065416] ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 30, 2017, 3:26pm UTC](https://discuss.elastic.co/t/100-peak-of-processing-in-one-of-the-machines/76992/6 "2017-03-30T15:26:54Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.