[SERVER-67278] Write kAborted to disk when shard split cannot proceed due to an invalid config Created: 14/Jun/22 Updated: 29/Oct/23 Resolved: 15/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Didier Nadeau | Assignee: | Didier Nadeau |
| 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: | Server Serverless 2022-07-25 | ||||
| Participants: | |||||
| Linked BF Score: | 15 | ||||
| Description |
|
If the replica set config is invalid (missing recipient nodes, etc) we currently set the decision promise to kAborted and immediately return without updating the state document. This means we leave the state document in its initial state. Therefore if the current primary steps down, the next primary will try to "resume" the operation using this stale state document. It also means other shard split might not be able to work as there currently is an "active" shard split. |
| Comments |
| Comment by Githook User [ 15/Jul/22 ] |
|
Author: {'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}Message: |