# Stopping Elasticsearch using 'systemctl stop elasticsearch.service' operation consistently fails

**URL:** <https://discuss.elastic.co/t/stopping-elasticsearch-using-systemctl-stop-elasticsearch-service-operation-consistently-fails/357126>\
**Category:** Elasticsearch\
**Created:** [April 10, 2024, 10:38am UTC](https://discuss.elastic.co/t/stopping-elasticsearch-using-systemctl-stop-elasticsearch-service-operation-consistently-fails/357126 "2024-04-10T10:38:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mitanshu\_Bhoot](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mitanshu_bhoot/32/133413_2.png) [@Mitanshu\_Bhoot](https://discuss.elastic.co/u/Mitanshu_Bhoot)\
**Post date:** [April 10, 2024, 10:38am UTC](https://discuss.elastic.co/t/stopping-elasticsearch-using-systemctl-stop-elasticsearch-service-operation-consistently-fails/357126/1 "2024-04-10T10:38:00Z")

</div>

Elasticsearch's stop operation fails when attempting to gracefully stop using the systemctl command. The node contains a substantial amount of data, around 10TBs with 200 shards. ES version is 8.9. Is there any solution to this issue?

Some background: I need to periodically resize the data disks on the node to increase storage capacity. Therefore, I first need to stop Elasticsearch, but the stop operation fails.

Additionally, is it possible to temporarily modify the Elasticsearch service configuration to prevent auto-start during the resizing process, and then revert it back to its original configuration afterward?