# We have facing some issue with elastic search 8.15.1

**URL:** <https://discuss.elastic.co/t/we-have-facing-some-issue-with-elastic-search-8-15-1/374113>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [February 5, 2025, 10:06am UTC](https://discuss.elastic.co/t/we-have-facing-some-issue-with-elastic-search-8-15-1/374113 "2025-02-05T10:06:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![calvin01](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@calvin01](https://discuss.elastic.co/u/calvin01)\
**Post date:** [February 5, 2025, 10:06am UTC](https://discuss.elastic.co/t/we-have-facing-some-issue-with-elastic-search-8-15-1/374113/1 "2025-02-05T10:06:24Z")

</div>

Hello Community,

We are running an **Elasticsearch 8.15.1 cluster** with **7 nodes** , each configured with **-Xms28g -Xmx28g** heap memory. Additionally, we have set `vm.max_map_count=262144` on the instances.

Unfortunately, our Elasticsearch cluster has become **unresponsive** , causing **timeouts across all applications**. We have checked the logs of all Elasticsearch pods in Kubernetes, but there are no error messages—only **INFO and WARN logs** related to **sharding and replication**.

Can anyone help us debug this issue using **Kibana DevTools** to confirm whether the problem lies with **Elasticsearch** or if it is caused by an **underlying network issue in the Kubernetes cluster**? Any guidance on identifying potential bottlenecks would be greatly appreciated.

Thanks!