-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
MongoClient does not mark a server Unknown when handling NotMaster errors embedded in a write concern error. We never implemented this prose test: https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/server-discovery-and-monitoring-tests.rst#node-is-recovering-error-from-a-write-concern-error
The following command responses should mark the server Unknown:
{ok:1, writeConcernError: {code: 91, codeName: "ShutdownInProgress"}} {ok:1, writeConcernError: {code: 189, codeName: "PrimarySteppedDown"}} {ok:1, writeConcernError: {code: 11600, codeName: "InterruptedAtShutdown"}} {ok:1, writeConcernError: {code: 11602, codeName: "InterruptedDueToReplStateChange"}} etc...
- related to
-
PYTHON-2340 Implement SDAM prose test for "Node is recovering" error from a write concern error
- Backlog
-
PYTHON-2199 Reduce race conditions in SDAM error handling
- Closed