[SERVER-76842] PreImagesTruncateMarkersPerCollection aren't removed when a collection is dropped Created: 04/May/23 Updated: 15/May/23 Resolved: 15/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Jordi Olivares Provencio |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Sprint: | Execution Team 2023-05-29 | ||||||||
| Participants: | |||||||||
| Description |
|
While its straightforward to drop an entire set of truncate markers when a tenant's config.preimages collection is dropped, knowing when a set of PreImagesTruncateMarkersPerCollection is safe to remove requires more effort. We need to ensure the pre-images associated with a dropped collection namespace are preserved until they expire. Additionally, we need to prevent leaking memory by having truncate markers associated with the dropped collection stay around forever. |
| Comments |
| Comment by Jordi Olivares Provencio [ 15/May/23 ] |
|
Closing as duplicate of |