[SERVER-67477] Ensure range deletion index is created on addShard (6.0 only) Created: 23/Jun/22 Updated: 29/Oct/23 Resolved: 29/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| 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 EMEA 2022-07-11, Sharding EMEA 2022-07-25, Sharding EMEA 2022-08-08 | ||||||||
| Participants: | |||||||||
| Description |
|
The index creation for range deletions happens in _shardingOnTransitionToPrimaryHook however, this code will not be run in the case that a shard is added for the first time to a cluster using addShard because the ShardingState is not necessarily enabled when the hook is run. This was fixed on version 6.1 by This ticket is to backport that fix to 6.0. |
| Comments |
| Comment by Allison Easton [ 29/Jul/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |
| Comment by Allison Easton [ 29/Jun/22 ] |
|
The fix for this was added as a part of the commit for |