[SERVER-61864] Replica set reconfiguration should check it's not removing a custom write concern which is set as the default Created: 02/Dec/21  Updated: 29/Oct/23  Resolved: 04/Apr/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Gabriel Marks Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-60817 setDefaultRWConcern accepts invalid w... Closed
related to SERVER-64309 Modify the server to support the set... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2022-02-21, Repl 2022-03-07, Repl 2022-03-21, Repl 2022-04-04, Repl 2022-04-18
Participants:

 Description   

As specified here: https://docs.mongodb.com/manual/reference/replica-configuration/#mongodb-rsconf-rsconf.settings.getLastErrorModes Custom-named write concerns can be set in the config, and then used as the default write concern. Currently, we can have the case where the default write concern is a custom write concern, and then the replica set is reconfigured to remove the custom write concern, so we are left with an invalid default write concern. Checks should be added to ensure such a reconfig fails.



 Comments   
Comment by Githook User [ 02/Apr/22 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-61864 Disallow removing custom write concern during reconfig if it is currently set as the default
Branch: master
https://github.com/mongodb/mongo/commit/ce3e917bfb81b54c3ded7b3f64692f666ddb2162

Generated at Thu Feb 08 05:53:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.