# 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:** 3\
**Page:** 2

<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 😃

---

<div class="post-metadata">

**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:** [May 31, 2021, 4:58pm UTC](https://discuss.elastic.co/t/node-sync-fails-and-cluster-goes-to-red/274409/22 "2021-05-31T16:58:37Z")

</div>

> [@parthmaniar](#):
>
> I wanted to ask if it is worthwhile for metricbeat or other component of Elastic Stack to keep an eye on disk errors?

IMO yes, see e.g. [Collect SMART data with metricbeat · Issue #8614 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/8614) and [report disk failures · Issue #20562 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/20562) but it's far from easy since SMART metrics are hard to read and not a very reliable indicator, and the log messages are even harder to identify.

---

<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:** [June 28, 2021, 4:58pm UTC](https://discuss.elastic.co/t/node-sync-fails-and-cluster-goes-to-red/274409/23 "2021-06-28T16:58:44Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

[Previous page](https://discuss.elastic.co/t/node-sync-fails-and-cluster-goes-to-red/274409.md?page=1)