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 reportsNOSPACE, 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-09-04 UTC."],[],[],null,["# Troubleshoot etcd for GKE on AWS\n\nThis pages shows you how to resolve issues with etcd for GKE on AWS.\nIf you need additional assistance, reach out to [Cloud Customer Care](/kubernetes-engine/multi-cloud/docs/aws/getting-support).\n\netcd data disk is full\n----------------------\n\nThe following error occurs when the etcd data disk is full, and might be\nobserved in a few different ways:\n\n- The etcd logs might show timeout errors for writing requests:\n\n rafthttp: failed to save KV snapshot (write /var/etcd/data/member/snap/tmp720030520: no space left on device)\n\n You might also see timeout errors for connections to peers: \n\n rafthttp: health check for peer [peer-id] could not connect: dial tcp [peer-ip]:2380: i/o timeout\n etcd server doesn't start:\n\n- The serial port logs might indicate that etcd can't start due to lack of space:\n\n failed on file /dev/stdout (No space left on device)\n\nTo determine the size of your etcd instance, use one of the following methods: \n\n### SSH\n\n1. Connect to one of the master nodes using SSH and run the following command:\n\n ETCDCTL_API=3 etcdctl --write-out=table endpoint status\n\n The `DB_SIZE` column indicates the size used, as shown in the following\n condensed example output: \n\n +------------------+------------------+---------+---------+\n | ENDPOINT | ID | VERSION | DB SIZE |\n +------------------+------------------+---------+---------+\n | 10.240.0.17:2379 | 4917a7ab173fabe7 | 3.5.0 | 45 kB |\n | 10.240.0.18:2379 | 59796ba9cd1bcd72 | 3.5.0 | 45 kB |\n | 10.240.0.19:2379 | 94df724b66343e6c | 3.5.0 | 45 kB |\n +------------------+------------------+---------+---------+\n\n### Console\n\n1. In the console, go to the Cloud Monitoring page.\n\n [Go to the Cloud Monitoring page](https://console.cloud.google.com/monitoring/)\n2. Select **Metrics explorer**.\n\n3. Select the `metric etcd_mvcc_db_total_size_in_bytes` metric.\n\nTo resolve this issue, resize the data disk for etcd using the appropriate\nprocedure for your storage provider and operating system. Add enough additional\nspace to account for future etcd growth.\n\n1. After the disk is resized, check if there's still a warning on disk space:\n\n ETCDCTL_API=3 etcdctl alarm list\n\n2. If the last column reports `NOSPACE`, disarm the alarm as follows:\n\n ETCDCTL_API=3 etcdctl alarm disarm\n\nWhat's next\n-----------\n\nIf you need additional assistance, reach out to [Cloud Customer Care](/kubernetes-engine/multi-cloud/docs/aws/getting-support)."]]
