[SERVER-76159] Image collection entry is not invalidated when update fails during initial sync Created: 14/Apr/23 Updated: 14/Jul/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | repl-shortlist | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 5 | ||||||||||||||||
| Description |
|
When we fail to update during initial sync because of missing document, we would return an error immediately (which will then be ignored) without invalidating the image_collection entry. But due to the same reason as matthew.russotto@mongodb.com mentioned here, a mismatched entry with a different txnNum should have no impact to correctness (% anonymous error code instead of IncompleteTransactionHistory). |
| Comments |
| Comment by Lingzhi Deng [ 14/Apr/23 ] |
|
I think the way writeToImageCollection is called now is pretty fragile. It seems it could be very easy to miss this call in one of the many exit paths in initial sync oplog application. We have seen |