[SERVER-78152] Lock the config server primary via fsync with lock command Created: 15/Jun/23 Updated: 29/Oct/23 Resolved: 26/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nandini Bhartiya | Assignee: | David Chen (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding NYC
|
| Backwards Compatibility: | Minor Change |
| Participants: | |
| Story Points: | 3 |
| Description |
|
Add logic in the mongos fsync command to lock the config shard primary. On failure to do lock the config server primary, all locked shards must be unlocked and an appropriate error must be returned to the user. |