[SERVER-58744] applyOps on capped collections can violate the multi-timestamp constraint Created: 22/Jul/21 Updated: 29/Oct/23 Resolved: 23/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 5.0.1 |
| Fix Version/s: | 5.0.3, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||||||||||||||||||||||||
| Steps To Reproduce: |
|
||||||||||||||||||||||||||||||||||
| Sprint: | Execution Team 2021-07-26 | ||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||
| Description |
|
An applyOps command on a capped collection that needs capped deletes violates the multi-timestamp constraint today. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] | ||
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! | ||
| Comment by Githook User [ 09/Aug/21 ] | ||
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit 4b9d7175b46a802e180b575aecf3292434fff8f4) | ||
| Comment by Githook User [ 22/Jul/21 ] | ||
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: | ||
| Comment by Bruce Lucas (Inactive) [ 22/Jul/21 ] | ||
|
For searchability, one manifestation of this issue is the following assertion failure when using mongomirror:
|