Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.3.0
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Security 2022-01-24, Replication 2021-12-13, Replication 2021-12-27, Replication 2022-01-10
Case:
Linked BF Score:
167
Confidence Status:
None
Work Order:
0

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

setDefaultRWConcern accepts invalid write concern options like {w: "1"}, but the server will error with UnknownReplWriteConcern when trying to do an actual write.

We should either start accepting {w: "1"} or error at the time of setting the default read/write concern.

causes

SERVER-87085 setDefaultRWConcern on sharded cluster doesn't validate defaultWriteConcern

In Progress

is related to

SERVER-61864 Replica set reconfiguration should check it's not removing a custom write concern which is set as the default

Closed

related to

SERVER-64309 Modify the server to support the setRWConcernDefault command directly against shardsvrs

Closed

Assignee:: Gabriel Marks

Reporter:: Samyukta Lanka

Participants:: Gabriel Marks, Githook User, Moustafa Maher, Samyukta Lanka

Votes:: 0 Vote for this issue

Watchers:: 10 Start watching this issue

Created:: Oct 19 2021 02:59:55 PM UTC

Updated:: Mar 11 2025 01:20:33 PM UTC

Resolved:: Jan 20 2022 05:20:05 PM UTC

Confidence Status Last Update:: 19/Jan/22 5:09 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates