# Bug Report : Memory leak when readiness probe Curls to check the cluster health when security is enabled

**URL:** <https://discuss.elastic.co/t/bug-report-memory-leak-when-readiness-probe-curls-to-check-the-cluster-health-when-security-is-enabled/193445>\
**Category:** Elasticsearch\
**Created:** [August 2, 2019, 5:24am UTC](https://discuss.elastic.co/t/bug-report-memory-leak-when-readiness-probe-curls-to-check-the-cluster-health-when-security-is-enabled/193445 "2019-08-02T05:24:34Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![Cyril\_James](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cyril_james/32/47277_2.png) [@Cyril\_James](https://discuss.elastic.co/u/Cyril_James)\
**Post date:** [August 5, 2019, 5:09am UTC](https://discuss.elastic.co/t/bug-report-memory-leak-when-readiness-probe-curls-to-check-the-cluster-health-when-security-is-enabled/193445/21 "2019-08-05T05:09:50Z")

</div>

> [@DavidTurner](#):
>
> consumer despite only having 1.5MB resident

Thanks David. Then we may have to look more into the part where we do the curl request and also verify any bug with kernel causing this memory issue.

---

<div class="post-metadata">

**Author:** ![Marc\_Wolff](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marc_wolff/32/45055_2.png) [@Marc\_Wolff](https://discuss.elastic.co/u/Marc_Wolff)\
**Post date:** [August 21, 2019, 8:34am UTC](https://discuss.elastic.co/t/bug-report-memory-leak-when-readiness-probe-curls-to-check-the-cluster-health-when-security-is-enabled/193445/22 "2019-08-21T08:34:32Z")

</div>

Hi Cyril,  
have you found a solution for that problem?

We have the same issue with https.  
Our settings are close:  
CentOS 7.6  
K8s: 1.14  
Docker 18.09.7

I think the RSS from the java process is not the problem.  
But i don´t know why the node mem limit is reached.

memory.stats:  
rss 1451929600

memory.usage\_in\_bytes:  
2137989120 and growing

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/5/759d12e0f2966d2f338599d6c7fb138d37cf8a2d.png)

---

<div class="post-metadata">

**Author:** ![Marc\_Wolff](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marc_wolff/32/45055_2.png) [@Marc\_Wolff](https://discuss.elastic.co/u/Marc_Wolff)\
**Post date:** [August 21, 2019, 12:50pm UTC](https://discuss.elastic.co/t/bug-report-memory-leak-when-readiness-probe-curls-to-check-the-cluster-health-when-security-is-enabled/193445/23 "2019-08-21T12:50:29Z")

</div>

My workaround for this problem is change readinessprobe

httpGet:  
httpHeaders:  
- name: Authorization  
value: Basic [base64 encoded user:pw]  
path: /\_cluster/health?local=true  
port: 9200  
scheme: HTTPS

---

<div class="post-metadata">

**Author:** ![Cyril\_James](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cyril_james/32/47277_2.png) [@Cyril\_James](https://discuss.elastic.co/u/Cyril_James)\
**Post date:** [August 21, 2019, 1:24pm UTC](https://discuss.elastic.co/t/bug-report-memory-leak-when-readiness-probe-curls-to-check-the-cluster-health-when-security-is-enabled/193445/24 "2019-08-21T13:24:11Z")

</div>

This seem to be an issue caused by Centos kernel bug.

---

<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:** [September 18, 2019, 1:38pm UTC](https://discuss.elastic.co/t/bug-report-memory-leak-when-readiness-probe-curls-to-check-the-cluster-health-when-security-is-enabled/193445/25 "2019-09-18T13:38:21Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/bug-report-memory-leak-when-readiness-probe-curls-to-check-the-cluster-health-when-security-is-enabled/193445.md?page=1)