# CPU overload due to a java exception

**URL:** <https://discuss.elastic.co/t/cpu-overload-due-to-a-java-exception/42857>\
**Category:** Elasticsearch\
**Created:** [February 26, 2016, 1:52pm UTC](https://discuss.elastic.co/t/cpu-overload-due-to-a-java-exception/42857 "2016-02-26T13:52:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vmichalak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vmichalak/32/8108_2.png) [@vmichalak](https://discuss.elastic.co/u/vmichalak)\
**Post date:** [February 26, 2016, 1:52pm UTC](https://discuss.elastic.co/t/cpu-overload-due-to-a-java-exception/42857/1 "2016-02-26T13:52:39Z")

</div>

Hi everyone,  
I have a problem. The load Average of my server up abnormally during 5 minutes randomly during the day. I checked my elasticsearch logs and i saw :

`[2016-02-26 12:55:54,106][WARN][http.netty] [elasticsearch-node-1] Caught exception while handling client http traffic, closing connection [id: 0xb472ab56, /127.0.0.1:52092 => /127.0.0.1:17198] java.io.IOException: Connexion ré-initialisée par le correspondant at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:192) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:384) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:64) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)`

I only have logstash and kibana in communication with my elastic search.

Any ideas ?

---

<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:** [February 26, 2016, 11:23pm UTC](https://discuss.elastic.co/t/cpu-overload-due-to-a-java-exception/42857/2 "2016-02-26T23:23:14Z")

</div>

What version are you on?

---

<div class="post-metadata">

**Author:** ![vmichalak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vmichalak/32/8108_2.png) [@vmichalak](https://discuss.elastic.co/u/vmichalak)\
**Post date:** [February 28, 2016, 4:01pm UTC](https://discuss.elastic.co/t/cpu-overload-due-to-a-java-exception/42857/3 "2016-02-28T16:01:37Z")

</div>

I use the latest version of elasticsearch / kibana and logstash.

---

<div class="post-metadata">

**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:** [February 29, 2016, 7:18pm UTC](https://discuss.elastic.co/t/cpu-overload-due-to-a-java-exception/42857/4 "2016-02-29T19:18:17Z")

</div>

Hello, look like a network issue between logstash and elasticsearch, maybe a too big bulk size.

Can you post your logstash configuration and CLI options. And runs HTTP GET "{ES}/\_nodes/stats/thread\_pool" to see if bulk threads pool is normal or not.

---

<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:12pm UTC](https://discuss.elastic.co/t/cpu-overload-due-to-a-java-exception/42857/5 "2017-07-05T23:12:48Z")

</div>