[SERVER-34501] Remove the config server code which upconverts all writeConcern to majority Created: 16/Apr/18  Updated: 06/Dec/22  Resolved: 16/Apr/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-34212 Config servers should only upconvert ... Closed
Related
related to SERVER-67874 Remove config server code which upcon... Closed
Assigned Teams:
Sharding
Participants:

 Description   

In MongoDB version 3.2 when CSRS was introduced, there were cases where commands coming from mongos did not specify write concern. For this purpose, the config server by default upconverts the writeConcern to majority. With the current codebase, this upconversion is no longer necessary because all mongos and shard commands against the config server should be including a write concern.

This ticket is to add testing that writeConcern:majority is always included with writes against the config server and to remove the upconversion code.


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