[SERVER-37172] rollbackViaRefetch should not update documents in capped collections Created: 17/Sep/18 Updated: 06/Dec/22 Resolved: 15/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | replication-rollbackviarefetch | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
In rollbackViaRefetch, when we roll back changes to a document and the document exists on the source, we perform an update on the document. This is problematic for capped collections, since updates in capped collections must not change the size of the document. For capped collections, we should instead truncate the collection (like we do for deletes) and then insert the source's version of the document. |
| Comments |
| Comment by Tess Avitabile (Inactive) [ 15/Jan/20 ] |
|
We are not fixing bugs where rollbackViaRefetch experiences and unrecoverable failure. |