Details
Description
This is because the ping update write command is being rejected by v3.2 config servers:
{ ok: 0, code: 2, errmsg: "w:1 and w:'majority' are the only valid write concerns when writing to config servers, got: { w: 0, wtimeout: 0 }" }
|
Attachments
Issue Links
- is related to
-
SERVER-21586 Investigate v3.0 mongos and v3.2 cluster compatibility issues in jstests/sharding
-
- Closed
-