[SERVER-4403] be more careful about sharded collections changing while creating indexes Created: 01/Dec/11 Updated: 21/Dec/22 Resolved: 21/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | pm-1051-legacy-tickets, sharding-common-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding EMEA
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
it's possible that our mongos isn't totally up to date with shard version when asked to create a new sharded index, and/or a migration could be occurring at the same time. We should probably continue to retry creating indices on newly discovered shards until our version doesn't change in the meantime. 99% of the time, this should only happen once. |
| Comments |
| Comment by Connie Chen [ 21/Dec/22 ] |
|
We believe this has already been addressed overtime due to the age of this ticket. Creating indexes has been improved through multiple projects. |
| Comment by Sheeri Cabral (Inactive) [ 31/Oct/19 ] |
|
"Each Shard has Correct Indexes" will fix this. |
| Comment by Greg Studer [ 01/Dec/11 ] |
|
Also, sharded index builds can silently fail, for example if there's an invalid point in the geo indexes |