[SERVER-55677] Remove resharding's DonorStateEnum::kPreparingToBlockWrites state Created: 31/Mar/21 Updated: 29/Oct/23 Resolved: 10/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2021-05-17 | ||||||||
| Participants: | |||||||||
| Story Points: | 1 | ||||||||
| Description |
|
Donor shards engage the critical section on the collection being resharded during the shard version refresh with CoordinatorStateEnum::kBlockingWrites. Not engaging the critical section during the shard version refresh would be data loss because on recovery, from a primary failover, the donor shard would be allowing new incoming writes possibly after it had written the final resharding oplog entries already. The DonorStateEnum::kPreparingToBlockWrites state therefore provides no benefit and can safely be removed. |
| Comments |
| Comment by Githook User [ 10/May/21 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |