[SERVER-77136] Introduce retry logic into bulkWrite override Created: 15/May/23 Updated: 27/Oct/23 Resolved: 26/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Trivial - P5 |
| Reporter: | Sean Zimmerman | Assignee: | Backlog - Replication Team |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | milestone-4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
For the bulkWrite override when we are flushing a bulkWrite command there is a possibility it will fail due to network error. We cannot rely on `network_error_and_txn_override` to do this for us because we are overriding runCommand to run the bulkWrite before the original command. We should be able to reuse logic / methods from network_error_and_txn_override but cannot rely on its existence.
This is probably actually not needed as long as we include network_error_and_txn_override after the bulkWrite override to get the retry logic |
| Comments |
| Comment by Sean Zimmerman [ 26/May/23 ] |
|
After further investigation this work isn't necessary as long as we apply the bulk write override before any other ones |