[SERVER-35083] Extend failCommand to return write concern errors Created: 18/May/18 Updated: 29/Oct/23 Resolved: 31/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc2, 4.1.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kevin Albertson | Assignee: | Mathias Stearn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||||||||||
| Sprint: | Platforms 2018-06-04 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Retryable writes now retries upon receiving a write concern error. It'd be nice to add tests to check this in our spec tests. Currently (per
Can we extend the failCommand failpoint to return write concern errors? Something like the following:
|
| Comments |
| Comment by Githook User [ 31/May/18 ] |
|
Author: {'username': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}Message: It replaces the waitForWriteConcern logic with just adding the supplied (cherry picked from commit 8fcb4e1bbc38f2c87ff6b63bf305e2695218f103) |
| Comment by Githook User [ 31/May/18 ] |
|
Author: {'username': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}Message: It replaces the waitForWriteConcern logic with just adding the supplied |