[SERVER-51297] Allow writeErrors to be specified via failCommand Created: 01/Oct/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Divjot Arora (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | sa-remove-fv-backlog-22 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Story Points: | 4 | ||||||||||||||||
| Description |
|
Drivers can currently use failCommand to have the server return {ok: 0} errors and errors in a writeConcernError document. Would it be possible to augment this functionality to return errors in a writeErrors array as well? The motivation for doing so is to test DRIVERS-555. One of the requirements for the project is to convert errors with code 50 (MaxTimeMSExpired) into a client-side TimeoutException. This error can be returned via {ok: 0}, writeErrors, or writeConcernError, so we'd like to be able to test all three formats via failpoints.
Acceptance Criteria: Add a new option to the failCommand command that allows users to inject an array of write errors. |
| Comments |
| Comment by Benji Rewis (Inactive) [ 22/Feb/22 ] |
|
This issue came up again the Go driver with GODRIVER-2320. We could use a potential writeErrors field in failCommand to test the processing of WriteErrors with deletes. |