Details
-
Bug
-
Resolution: Fixed
-
Critical
-
Cheshire-Cat
-
None
-
Untriaged
-
1
-
Unknown
-
KV-Engine 2021-March
Description
The disk utilisation tracking for collections isn't accounting for tombstone purging.
E.g.
- store k1 -> disk size = 80
- del k1 -> disk size = 16 (tombstone is accounted)
- later compact and purge -> disk size = 16
Attachments
Issue Links
For Gerrit Dashboard: MB-45132 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
149231,3 | MB-45132: 1/n Read vbstate using getLocalVbState | master | kv_engine | Status: MERGED | +2 | +1 |
149232,4 | MB-45132: 2/n use a single loop when processing collection stats | master | kv_engine | Status: MERGED | +2 | +1 |
149233,3 | MB-45132: 3/n use std::move to remove a copy of the collectionSizes map | master | kv_engine | Status: MERGED | +2 | +1 |
149234,1 | MB-45132: 4/n Update collection diskSize for purged tombstones | master | kv_engine | Status: ABANDONED | 0 | -1 |
149499,6 | MB-45132: 4/n Account for purged tombstones in collection stats | master | kv_engine | Status: MERGED | +2 | +1 |