Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Minor Change
-
Repl 2021-05-03, Repl 2021-05-17
-
(copied to CRM)
-
159
Description
- We will fassert on startup if the field exists and is not
{w:1, wtimeout: 0}
for a replica set that is part of a sharded cluster, since that would be counter to our goal of ensuring that the default write concern is uniform across all replica sets in the cluster.
- We will fail any addShard for a replica set that specifies something other than
{w:1, wtimeout: 0}
or any replSetReconfig commands that modify getLastErrorDefaults.
- We should upgrade the existing startup warning for non
{w:1, wtimeout: 0}
values on non-shard servers from saying that this field is deprecated to say that the field is ignored.
Attachments
Issue Links
- is documented by
-
DOCS-14440 Investigate changes in SERVER-56241: Don't allow setting getLastErrorDefaults on startup/reconfig
-
- Closed
-
- is duplicated by
-
SERVER-55694 Upgrade startup warning for getLastErrorDefaults
-
- Closed
-