# Problème Elasticsearch every milliseconde

**URL:** <https://discuss.elastic.co/t/probleme-elasticsearch-every-milliseconde/115651>\
**Category:** Elasticsearch\
**Created:** [January 16, 2018, 7:25am UTC](https://discuss.elastic.co/t/probleme-elasticsearch-every-milliseconde/115651 "2018-01-16T07:25:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![adrien-vinet](https://avatars.discourse-cdn.com/v4/letter/a/e19adc/32.png) [@adrien-vinet](https://discuss.elastic.co/u/adrien-vinet)\
**Post date:** [January 16, 2018, 7:25am UTC](https://discuss.elastic.co/t/probleme-elasticsearch-every-milliseconde/115651/1 "2018-01-16T07:25:26Z")

</div>

Hello all,

I contact you because I have a problem with my elasticsearch server.

My configuration :

- Serveur front whit haproxy
- 2 serveurs with elastic search

My haproxy configuration :

```auto
listen elasticsearch-cluster
	bind 127.0.0.1:9200
        option httpchk
        balance roundrobin
    	server ipvr5.yoomap 172.16.0.5:9200 check
    	server ipvr6.yoomap 172.16.0.6:9200 check backup

```

My elasticsearch configuration (version 2.4.4) :

```auto
# Elasticsearch 2.X configuration for Yoomap
cluster.name: yoomap_preprod_2
http.port: 9200
node.name: s5.yoomap
discovery.zen.ping.unicast.hosts: ["172.16.0.5", "172.16.0.6"]
network.host: [_eth1_]
network.bind_host: [_eth1_]
node.data: true
node.master: true
bootstrap.mlockall: true
index.query.bool.max_clause_count: 4096
action.auto_create_index: false

```

I have this problem on the log file :

```auto
[2018-01-16 07:45:06,244][WARN][http.netty] [s5.yoomap] Caught exception while handling client http traffic, closing connection [id: 0x532248d5, /172.16.0.5:53849 => /172.16.0.5:9200]
java.io.IOException: Connection re-initialized by the correspondent
	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)

```

Do you have a solution to this problem?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 16, 2018, 7:39am UTC](https://discuss.elastic.co/t/probleme-elasticsearch-every-milliseconde/115651/2 "2018-01-16T07:39:46Z")

</div>

Bonjour!

I believe this is a problem with HAProxy (I'm not an expert at all of that).

I found this gist on Github about HA Proxy and elasticsearch and that might help:

> <https://gist.github.com/tebeka/c96887c2ddcebb752a81>

---

<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:** [February 13, 2018, 7:40am UTC](https://discuss.elastic.co/t/probleme-elasticsearch-every-milliseconde/115651/3 "2018-02-13T07:40:35Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.