[SERVER-66683] Archive eligible buckets instead of closing them Created: 23/May/22 Updated: 29/Oct/23 Resolved: 15/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Dan Larkin-York |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Execution Team 2022-06-13, Execution Team 2022-06-27 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 35 | ||||||||||||
| Description |
|
When a given bucket is eligible to receive more measurements, but we are about to close it e.g. due to memory pressure or out-of-order inserts, we should instead archive it. We will need to create a new list of archived buckets in BucketCatalog::Stripe, where we will retain the hash of the BucketKey and the bucket's _id value. We will need to keep track of the archived list's memory usage. |
| Comments |
| Comment by Githook User [ 14/Jun/22 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |