[SERVER-22876] Ensure 'majority' writes are possible before entering the migration critical section Created: 26/Feb/16 Updated: 06/Dec/22 Resolved: 12/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.3, 3.3.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
The moveChunk command should do a best-effort check that the CSRS config server's primary can do majority writes before entering the critical section on the shard. This will shorten the window where a badly timed loss of quorum on the config server might cause the migration critical section to fail. |
| Comments |
| Comment by Andy Schwerin [ 27/Feb/16 ] |
|
It is also important that this check be done before setting the flag indicating recovery is required in the minOptimeRecovery document, so that a prolonged lack of csrs primary doesn't prevent new shard primary nodes from exiting drain mode. |