# Elastic serach going unresponsive

**URL:** <https://discuss.elastic.co/t/elastic-serach-going-unresponsive/354505>\
**Category:** Elasticsearch\
**Created:** [March 1, 2024, 5:56am UTC](https://discuss.elastic.co/t/elastic-serach-going-unresponsive/354505 "2024-03-01T05:56:16Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [March 12, 2024, 2:31pm UTC](https://discuss.elastic.co/t/elastic-serach-going-unresponsive/354505/7 "2024-03-12T14:31:06Z")

</div>

You did not answer this question.

> [@dadoonet](#):
>
> How could you allocate more HEAP than the available RAM?

What is the exact HEAP size?

And

What is the output of:

```auto
GET /

```

Please format your code, logs or configuration files using `</>` icon as explained in [this guide](https://discuss.elastic.co/t/about-the-elasticsearch-category/21) and not the citation button. It will make your post more readable.

Or use markdown style like:

````
```
CODE
```

````

This is the icon to use if you are not using markdown format:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/e/7e6e239431ec2d71cbf1beef741f2e93e7cc762c.jpg)

There's a live preview panel for exactly this reasons.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.  
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.

I updated your post but please do it for the next one.

---

_[View the full topic](https://discuss.elastic.co/t/elastic-serach-going-unresponsive/354505)._