# Node sync fails and cluster goes to "red"

**URL:** <https://discuss.elastic.co/t/node-sync-fails-and-cluster-goes-to-red/274409>\
**Category:** Elasticsearch\
**Created:** [May 29, 2021, 7:27pm UTC](https://discuss.elastic.co/t/node-sync-fails-and-cluster-goes-to-red/274409 "2021-05-29T19:27:54Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![parthmaniar](https://avatars.discourse-cdn.com/v4/letter/p/71e660/32.png) [@parthmaniar](https://discuss.elastic.co/u/parthmaniar)\
**Post date:** [May 31, 2021, 1:37pm UTC](https://discuss.elastic.co/t/node-sync-fails-and-cluster-goes-to-red/274409/21 "2021-05-31T13:37:27Z")

</div>

Hello @DavidTurner , I wanted to thank you once again, the cluster is green, backed up and on a new disk 🙂 all of my research data is intact and now backed up locally on a NAS (with disk level redundancy) and in the cloud 😃 .

I wanted to ask if it is worthwhile for metricbeat or other component of Elastic Stack to keep an eye on disk errors? I know there isn't a specific module that looks at hardware health level but based on my experience it could be an excellent indicator to be monitored under **stack monitoring?**

If you feel this is a meaningful addition I can open a GitHub feature request. 🙂

Thank you and have a wonderful week ahead 😃

---

_[View the full topic](https://discuss.elastic.co/t/node-sync-fails-and-cluster-goes-to-red/274409)._
