# Correct way to reboot a node in 7.x cluster while data updates are happening

**URL:** <https://discuss.elastic.co/t/correct-way-to-reboot-a-node-in-7-x-cluster-while-data-updates-are-happening/253166>\
**Category:** Elastic Search\
**Created:** [October 23, 2020, 5:30pm UTC](https://discuss.elastic.co/t/correct-way-to-reboot-a-node-in-7-x-cluster-while-data-updates-are-happening/253166 "2020-10-23T17:30:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vmanohar1](https://avatars.discourse-cdn.com/v4/letter/v/e56c9b/32.png) [@vmanohar1](https://discuss.elastic.co/u/vmanohar1)\
**Post date:** [October 23, 2020, 5:30pm UTC](https://discuss.elastic.co/t/correct-way-to-reboot-a-node-in-7-x-cluster-while-data-updates-are-happening/253166/1 "2020-10-23T17:30:29Z")

</div>

Hi.. If the cluster with N nodes [at least 10] is getting constant data updates, how can one gracefully reboot a given node[for any maintenance work] that is master+data node?  
We do not want to loose any incoming updates during the time given node is rebooted. I did read some docs on this. But it was not quite clear.

Thank you. -V

---

<div class="post-metadata">

**Author:** ![vmanohar1](https://avatars.discourse-cdn.com/v4/letter/v/e56c9b/32.png) [@vmanohar1](https://discuss.elastic.co/u/vmanohar1)\
**Post date:** [November 19, 2020, 2:00pm UTC](https://discuss.elastic.co/t/correct-way-to-reboot-a-node-in-7-x-cluster-while-data-updates-are-happening/253166/2 "2020-11-19T14:00:53Z")

</div>

I figured it out..

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 4, 2022, 8:16am UTC](https://discuss.elastic.co/t/correct-way-to-reboot-a-node-in-7-x-cluster-while-data-updates-are-happening/253166/3 "2022-11-04T08:16:11Z")

</div>

Closed on November 4, 2022, 8:16am UTC