-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.4.9, 3.5.13
-
Component/s: Replication, Write Ops
-
None
-
Fully Compatible
-
ALL
-
v3.4
-
Query 2017-10-23
// Update the featureCompatibilityVersion document stored in the "admin.system.version" // collection. BSONObj updateResult; client.runCommand(nss.db().toString(), updateCmd.obj(), updateResult); uassertStatusOK(getStatusFromCommandResult(updateResult)); uassertStatusOK(getWriteConcernStatusFromCommandResult(updateResult));
Since this is doing an update, it can return a status like the following with ok:1 but a write error indicating that we should fail:
{ n: 0, nModified: 0, writeErrors: [ { index: 0, code: 62, errmsg: "Must be in primary or secondary state to downgrade feature compatibility version document { _id: "featureCompatibilityVersion", version: "3.4", targetV..." } ], ok: 1.0 }
- is depended on by
-
SERVER-31189 fassert if feature compatibility version changes during rollback
- Closed