[SERVER-55804] Provide option to not store findAndModify pre/post images with retryable writes Created: 05/Apr/21 Updated: 27/Oct/23 Resolved: 14/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Replication Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Sprint: | Repl 2021-04-19 | ||||
| Participants: | |||||
| Description |
|
These pre/post images consume a lot of oplog space and are only used in a subset of retry scenarios. We can offer retryability of the "modify" without offering retryability of the "find" if we don't store these pre/post images. We will build this into 4.0 and then forward port it as needed. |
| Comments |
| Comment by Judah Schvimer [ 16/Jun/21 ] |
|
This ticket was an alternative approach to reducing the oplog entry size of retryable findAndModify operations. Since we built a more complete solution in |