[SERVER-41219] Add writeConcern as a field in config.migrations Created: 17/May/19 Updated: 06/Dec/22 Resolved: 29/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | ShardingRoughEdges | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 20 | ||||
| Description |
|
If a config server steps down and a new primary recovers migrations from config.migrations, it will not know what write concern the initial request was sent with and can lead to reads on secondaries being incorrect. |
| Comments |
| Comment by Ratika Gandhi [ 29/Jul/19 ] |
|
BF only happened once. BF marked as Trivial. Will consider reopening if it happens again. |