# Elasticsearch 6.1.1 client running OOM and dumping heap

**URL:** <https://discuss.elastic.co/t/elasticsearch-6-1-1-client-running-oom-and-dumping-heap/201867>\
**Category:** Elasticsearch\
**Created:** [October 1, 2019, 8:45pm UTC](https://discuss.elastic.co/t/elasticsearch-6-1-1-client-running-oom-and-dumping-heap/201867 "2019-10-01T20:45:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cching](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cching/32/44800_2.png) [@cching](https://discuss.elastic.co/u/cching)\
**Post date:** [October 1, 2019, 8:45pm UTC](https://discuss.elastic.co/t/elasticsearch-6-1-1-client-running-oom-and-dumping-heap/201867/1 "2019-10-01T20:45:31Z")

</div>

We are having troubles with Elasticsearch 6.1.1 running in client mode. Basically it runs as a frontend for bulk requests from log stash and queries from Kibana. Analyzing the heap dump shows about half the memory is taken by the clientHandlers ConcurrentMapLong in Transport:

> <https://github.com/elastic/elasticsearch/blob/6.1/core/src/main/java/org/elasticsearch/transport/TransportService.java#L91>

Can anyone provide some insight into how we can prevent this? Is it possibly a memory leak? Happy to provide more information!

---

<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:** [October 29, 2019, 8:45pm UTC](https://discuss.elastic.co/t/elasticsearch-6-1-1-client-running-oom-and-dumping-heap/201867/2 "2019-10-29T20:45:32Z")

</div>

Closed on October 29, 2019, 8:45pm UTC

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