- 最新
- 投票最多
- 评论最多
Hi,
I hope you were able to find a solution to the issue, but if not, I can share some pointers:
-
Since you have a single node cluster, the missing metrics can be logically assumed a drop to zero when the node disappears and there isnt any metric sent to Cloudwatch. I assume with this setup you dont have dedicated master nodes, which would explain why there is a gap in node count metric
-
There is some finite amount of data that a single node can hold and that does not always correspond to the free disk space. There are multiple metrics like the JVM allocation, number of shards etc... On a single node cluster, I have seen node restart and data loss when the JVM Memory pressure goes beyond 75% for a longer duration. Also look for CPU / Memory utilization.
-
There are other metrics also that you can look for like cluster state being non-green. There is a possibility these other alert / metrics may precede the actual time of node restart and provide you a heads up about the issue.
-
You can trigger an alert for missing data to be treated as breaching threshold in Cloudwatch. That should notify you.
--Syd
相关内容
- AWS 官方已更新 1 年前