[SERVER-43941] Add "errorLabels" field to failCommand fail point Created: 10/Oct/19 Updated: 29/Oct/23 Resolved: 12/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Emily Giurleo (Inactive) | Assignee: | Lingzhi Deng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Repl 2019-10-21, Repl 2019-11-04, Repl 2019-11-18 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
To test retryable writes on the drivers, I'd like to be able to force the server to return errors with the RetryableWriteError label but a non-retryable error code, thus making sure that the driver responds acts in accordance to the error label and not the error code. Also update the The-"failCommand"-fail-point wiki page with any changes made to the failCommand fail point. That is currently the only documentation we have for the fail point, outside of some driver spec documents, so it'd be helpful to keep it up-to-date. |
| Comments |
| Comment by Lingzhi Deng [ 12/Nov/19 ] |
|
Also updated failCommand wiki page. |
| Comment by Githook User [ 12/Nov/19 ] |
|
Author: {'username': 'ldennis', 'email': 'lingzhi.deng@mongodb.com', 'name': 'Lingzhi Deng'}Message: |
| Comment by Emily Giurleo (Inactive) [ 10/Oct/19 ] |
|
judah.schvimerlingzhi.deng for visibility |