# Elasticsearch Force Restart taking a really long time

**URL:** <https://discuss.elastic.co/t/elasticsearch-force-restart-taking-a-really-long-time/364295>\
**Category:** Elasticsearch\
**Created:** [August 2, 2024, 10:11pm UTC](https://discuss.elastic.co/t/elasticsearch-force-restart-taking-a-really-long-time/364295 "2024-08-02T22:11:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vsabado](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@vsabado](https://discuss.elastic.co/u/vsabado)\
**Post date:** [August 2, 2024, 10:11pm UTC](https://discuss.elastic.co/t/elasticsearch-force-restart-taking-a-really-long-time/364295/1 "2024-08-02T22:11:31Z")

</div>

I hit a lot of issues while updating my deployment of Elasticsearch today. Reducing the RAM from 4GB down resulted in the JVM pressure getting really high. I've re-adjusted some of those changes but my Elasticsearch instance is now in an unhealthy state. I'm trying to force restart now in an attempt to get the deployment in a good enough place where I can attempt to upgrade the RAM again but this force restart has been going on now for 2 hours. I'm concerned that I've just ruined this deployment in some way

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/f/1f4953ab08838c0886daaca41e486b44fb1ad7d1.png)

These were the aborted config changes that I attempted prior:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/e/cec61ec48987162e2f1f1ee3a708f8aba632b3c5.png)