Setting a failpoint on mongos to return a writeConcernError containing a state change error code is rewritten to HostUnreachable (6). I think this is caused by the changes of SERVER-50549.
State change errors indicate the server has changed state (e.g. 91 = ShutdownInProgress or 10107=NotWritablePrimary). Drivers document the state change errors they check for in the Server Discovery and Monitoring specification.
Drivers expect failpoints on mongos to return the errors exactly as they are configured. This enables the test scenario of a mongos returning a state change error itself (instead of rewriting one from a backing mongod).
The writeConcernError in particular only affects one test in the C driver, and is easy to work around. This is not blocking driver tests currently.
- is related to
-
SERVER-58920 Enable multiversion testing of rewrite_state_change_errors.js
- Closed
-
SERVER-50549 Transform connection-related error codes in proxied commands
- Closed
- related to
-
CDRIVER-4022 Skip /WriteCommand/invalid_wc_server_error test on mongos
- Closed