Skip to content

Commit

Permalink
Merge pull request etcd-io#677 from geetasg/main
Browse files Browse the repository at this point in the history
Add object deletion as a solution to nospace alarm recovery
  • Loading branch information
ahrtr authored May 2, 2023
2 parents 623358f + 4618c4e commit 87f916d
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions content/en/blog/2023/how_to_debug_large_db_size_issue.md
Original file line number Diff line number Diff line change
Expand Up @@ -257,5 +257,7 @@ In the following example, there are two etcd clusters; one for the normal usage,
--etcd-servers-overrides="/events#https://etcd-3:2379,https://etcd-4:2379,https://etcd-5:2379"
```

As a mitigation, you may also want to delete unneeded objects to free up some space. You will need to delete objects before running compaction and defragmentation to free up the space.

If the behavior (db size exceeds the quota) isn't expected, then you'd better figure out the root cause and resolve
it firstly. If you insist on applying solutions mentioned above, it can mitigate the issue instead of resolving it.

0 comments on commit 87f916d

Please sign in to comment.