Version 1.15. This version is no longer supported. For information about how to upgrade to version 1.16, see Upgrade clusters in the latest documentation. For more information about supported and unsupported versions, see the Version history page in the latest documentation.
Select the metric etcd_mvcc_db_total_size_in_bytes metric.
To resolve this issue, resize the data disk for etcd using the appropriate
procedure for your storage provider and operating system. Add enough additional
space to account for future etcd growth.
After the disk is resized, check if there's still a warning on disk space:
ETCDCTL_API=3etcdctlalarmlist
If the last column reports NOSPACE, disarm the alarm as follows:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["This guide helps troubleshoot and resolve issues related to a full etcd data disk in Google Distributed Cloud."],["A full etcd data disk can cause errors such as timeout errors for writing requests or connection to peers and etcd server failing to start."],["You can determine the size of your etcd instance using SSH to a master node and checking the `DB_SIZE` or through Cloud Monitoring's Metrics explorer."],["Resolving a full etcd disk involves resizing the data disk with your storage provider to have enough additional space for future growth and growth."],["After resizing the disk, ensure to check for any remaining warnings and disarm the `NOSPACE` alarm if it is still present."]]],[]]