# Restart Elastic search without data loss single node cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [September 3, 2025, 3:03am UTC](https://discuss.elastic.co/t/restart-elastic-search-without-data-loss-single-node-cluster/381540 "2025-09-03T03:03:49Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Sudhir\_Takale1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sudhir_takale1/32/140879_2.png) [@Sudhir\_Takale1](https://discuss.elastic.co/u/Sudhir_Takale1)\ **Post date:** [September 3, 2025, 3:03am UTC](https://discuss.elastic.co/t/restart-elastic-search-without-data-loss-single-node-cluster/381540/1 "2025-09-03T03:03:50Z")
I want to restart my Elasticsearch service which is running on EC2, data stored on EFS mounted on EC2. As in current yml file there is no security related configurations present, I want add these and restart Elasticsearch service. Whether it will impact existing data, I'm using single node cluster . It is a production env. Please help! ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [September 3, 2025, 10:11am UTC](https://discuss.elastic.co/t/restart-elastic-search-without-data-loss-single-node-cluster/381540/2 "2025-09-03T10:11:02Z")
A one-node cluster will recover from a restart as long as the data on disk persists across the restart. Of course it will be unavailable while it’s restarting. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 3, 2025, 10:14am UTC](https://discuss.elastic.co/t/restart-elastic-search-without-data-loss-single-node-cluster/381540/3 "2025-09-03T10:14:24Z")
> [@Sudhir\_Takale1](#): > > data stored on EFS mounted on EC2 I recall issues using EFS for data storage with Elasticsearch, so would recommend switching to EBS. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [September 3, 2025, 10:59am UTC](https://discuss.elastic.co/t/restart-elastic-search-without-data-loss-single-node-cluster/381540/4 "2025-09-03T10:59:30Z")
> [@Christian\_Dahlqvist](#): > > issues using EFS Performance issues, not data loss tho. For light workloads it’s probably fine. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 3, 2025, 11:10am UTC](https://discuss.elastic.co/t/restart-elastic-search-without-data-loss-single-node-cluster/381540/5 "2025-09-03T11:10:44Z")
I vaguely recall EFS not behaving as a file system the way Elasticsearch requires. In [the docs](https://www.elastic.co/docs/reference/elasticsearch/plugins/cloud-aws-best-practices) it still states the following: > Historically, shared network filesystems such as EFS have not always offered precisely the behaviour that Elasticsearch requires of its filesystem, and this has been known to lead to index corruption. Is that no longer true? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [September 3, 2025, 11:29am UTC](https://discuss.elastic.co/t/restart-elastic-search-without-data-loss-single-node-cluster/381540/6 "2025-09-03T11:29:54Z")
> [@Christian\_Dahlqvist](#): > > I vaguely recall EFS not behaving as a file system the way Elasticsearch requires. Hmm not sure these days, I haven’t heard of anyone encountering such an issue for ages. But maybe that’s because not many people use EFS for this purpose rather than because they fixed the bugs.