[SERVER-15975] Dropped index can get recreated again in sharded clusters Created: 05/Nov/14 Updated: 06/Dec/22 Resolved: 06/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.7.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding EMEA
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Dropping an index that had been created on a shard that no longer had any chunks so the drop didn't go there. When a chunk is migrated to that shard and then back to original shard it has the effect of recreating a previously dropped index. |
| Comments |
| Comment by Kaloian Manassiev [ 06/Nov/21 ] |
|
Looks like this has gone away. |