-
Notifications
You must be signed in to change notification settings - Fork 9.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
mvcc: database space exceeded #10776
Comments
Probably. The actual answer depends on how much space is needed in your use case. This can be estimated by: How many keys are stored in etcd? How big are they? How often do they get updated?
Defrag blocks all reads and writes, so probably don't defrag frequently. I think a good practice is to monitor the db size frequently and only defrag if needed. |
@CH-anhngo the old etcd's storage size limit is small. Try to use the latest version, it can support 100GB data, I almost not run defrag any more since it's absolutely enough for my case. |
yep we are running the latest |
@CH-anhngo I guess we can close this issue but please reopen or create a new one if you feel a need. As it's mentioned in the issue comments, there aren't best practices that fits all but the documentations below discusses compaction, defrag, quota in more details which you might already read. |
@jingyih Curious to know more about estimation. Do you have any docs on how estimation can be done? Mainly interested to map frequency of updates to estimated size. |
we set
--auto-compaction-mode revision --auto-compaction-retention 25000
but usually gettingmvcc: database space exceeded
should we increase the
quota-backend-bytes
to bigger size ? or do folks have to run daily/hourly defrag ?what is best practice to benchmark the capacity ..etc ? how do we know we are under capacity regarding the db size ? #10312 #8009
The text was updated successfully, but these errors were encountered: