[SERVER-64631] Abort index builds before running shard split Created: 18/Mar/22 Updated: 29/Oct/23 Resolved: 24/May/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: | Matt Broadstone | Assignee: | Mathis Bessa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-05-16, Server Serverless 2022-05-30 |
| Participants: |
| Description |
|
Esha's investigation as part of WRITING-10501 discovered that voteCommitIndexBuild is not blocked by tenant access blockers, so index builds might hang forever waiting for quorum which never arrives. The best solution would be to leverage tenant access blockers to block voteCommitIndexBuild commands, but that work is very involved. As a stop-gap, the server should abort in-progress index builds before starting a shard split operation similar to tenant migrations. |
| Comments |
| Comment by Githook User [ 17/May/22 ] |
|
Author: {'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |