[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: |
|
||||||||||||||||
| 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. |