[SERVER-79632] Stop range deletion when hashed shard key index does not exist Created: 02/Aug/23 Updated: 29/Oct/23 Resolved: 01/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 5.0.22, 7.0.3, 6.0.12 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sanika Phanse (Inactive) | Assignee: | Sanika Phanse (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Requested: |
v7.0, v6.0, v5.0
|
||||||||||||||||||||
| Sprint: | Sharding NYC 2023-08-07, Sharding NYC 2023-08-21, Sharding NYC 2023-09-04 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 152 | ||||||||||||||||||||
| Description |
|
Currently, range deletion gets stuck searching for an index to complete an indexScan for deletion. In the case of a hashed shard key index, we will allow skipping range deletion for the collection. This may lead to orphan documents remaining on the shards, but we will solve this with documentation by recommending that a user drain orphan documents before deleting their index. |
| Comments |
| Comment by Githook User [ 06/Oct/23 ] |
|
Author: {'name': 'Sanika Phanse', 'email': 'sanika.phanse@mongodb.com', 'username': 'sphanse99'}Message: |
| Comment by Githook User [ 03/Oct/23 ] |
|
Author: {'name': 'Sanika Phanse', 'email': 'sanika.phanse@mongodb.com', 'username': 'sphanse99'}Message: |
| Comment by Githook User [ 19/Sep/23 ] |
|
Author: {'name': 'Sanika Phanse', 'email': 'sanika.phanse@mongodb.com', 'username': 'sphanse99'}Message: |
| Comment by Githook User [ 24/Aug/23 ] |
|
Author: {'name': 'Sanika Phanse', 'email': 'sanika.phanse@mongodb.com', 'username': 'sphanse99'}Message: |