[Feature] Defragmentor of backup-restore should also consider the etcd db size along with scheduled defrag #556
Labels
kind/enhancement
Enhancement, improvement, extension
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
priority/2
Priority (lower number equals higher priority)
Feature (What you would like to be added):
Defragmentor logic of backup-restore should also consider the
etcd db
size along with schedule time of defragmentation and if Defragmentor observed thatetcd db
size has crossed the certain limit(say 7Gi) which is close toetcd db quota bytes
then it should trigger the out-of-schedule defragmentation on etcd so thatetcd db
size won't crosses the practical limit of 8Gi.Motivation (Why is this needed?):
It has been observed that sometimes etcd's db size abruptly increases and cross the practical limit of 8Gi which leads to unavailability of etcd cluster. To resolve this we require the manual intervention to trigger the defragmentation on etcd, to avoid this manual intervention our defragmentor should smart enough to detect this and trigger the out-of-schedule defragmentation on etcd.
Approach/Hint to the implement solution (optional):
The text was updated successfully, but these errors were encountered: