# Http.current\_open **URL:** https://discuss.elastic.co/t/http-current-open/24019 **Category:** Elasticsearch **Created:** [June 19, 2015, 9:21pm UTC](https://discuss.elastic.co/t/http-current-open/24019 "2015-06-19T21:21:16Z") **Posts on this page:** 3 **Page:** 1
### Author: ![telendt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/telendt/32/3416_2.png) [@telendt](https://discuss.elastic.co/u/telendt) #### Post date: [June 19, 2015, 9:21pm UTC](https://discuss.elastic.co/t/http-current-open/24019/1 "2015-06-19T21:21:16Z")
Hi, I noticed a strange behavior in the cluster of Elasticsearch (v1.5.2) that we run in the company. For some of the nodes the value of `http.current_open` (and `process.open_file_descriptors`) reported by Node Stats is going up with time until some limit value (over 1k of `http.current_open`) is hit. When that happens `http.current_open` drops to more normal, one digit value. Right after that the problem reappears on different node(s). It's best to illustrate it with a graph (we use Elasticsearch StatsD plugin with push to Graphite): ![](https://us1.discourse-cdn.com/elastic/original/2X/2/263a6c0501dc3a6385ee6f7fd1a7bb961f7ada56.png) First of all I haven't found what http.current\_open really stands for. I assume that the number of open incoming TCP connection for it's HTTP transport (listening on port 9200 by default). The problem is that these numbers don't match: 1. I'm first identifying the node with most `http.current_open`: 2. Then I'm logging to this host checking and counting these connections myself: Can someone please explain to me why these numbers don't match? I'd also like to understand why does it happen. Our apps access the cluster via HAProxy (using round-robin) if that changes anything. It's probably worth to mention that the number of TCP connections reported by HAProxy don't match `http.current_open` either. Best, Tomasz ---
### Author: ![telendt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/telendt/32/3416_2.png) [@telendt](https://discuss.elastic.co/u/telendt) #### Post date: [August 21, 2015, 2:33pm UTC](https://discuss.elastic.co/t/http-current-open/24019/2 "2015-08-21T14:33:05Z")
Hi, I just wanted to write that we found out why `http.current_open` were piling up - it was caused by our custom ES plugin (which was blocking HTTP server thread). As for the `http.current_open` not matching TCP connections at port 9200 - my guess is that's because of HTTP pipelining. ---
### 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:54pm UTC](https://discuss.elastic.co/t/http-current-open/24019/3 "2017-07-05T23:54:35Z")