[SERVER-77740] Ignore oplog replication delete errors for Change Collections Created: 02/Jun/23 Updated: 29/Oct/23 Resolved: 19/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution EMEA Team 2023-06-26 |
| Participants: |
| Description |
|
With the change to use unreplicated truncates in change collections there might be some cases where the replicated delete by an older primary affects a non-existant document on the secondary. There is logic right now to ignore these errors for change stream pre-images, but not for change collections. |
| Comments |
| Comment by Githook User [ 19/Jun/23 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |