[SERVER-83070] Confirm proper operation: delete without insert Created: 09/Nov/23 Updated: 12/Dec/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Felipe Gasper | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | storex-shortlist | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Participants: | |||||
| Description |
|
In REP-3572 we saw a mongosync test failure due to awkward interaction between mongosync's "fruit collections" substitution logic and time-series collection TTLs. Along the way, I saw something weird: the destination cluster in that test run has these oplog events for a time-series buckets collection:
Note that there's no insert here. I've inquired to a few folks, all of whom seemed to regard this as strange behavior. It seems worth confirming that nothing actually wrong happened here. See REP-3572 for more details. |