[SERVER-45102] Sharded listIndexes should always target a shard that owns chunks Created: 12/Dec/19 Updated: 29/Oct/23 Resolved: 18/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Cheahuychou Mao |
| 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 2019-12-16, Sharding 2019-12-30 | ||||||||
| Participants: | |||||||||
| Description |
|
PM-1361 changed the sharded index commands to only target shards that own chunks for a collection, so it is no longer correct for listIndexes to always target the primary shard to return a collection's indexes. Instead listIndexes should always target the shard that owns the chunk $minKey belongs to, so repeated listIndexes typically target the same shard. |
| Comments |
| Comment by Githook User [ 18/Dec/19 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}Message: |
| Comment by Jack Mulrow [ 12/Dec/19 ] |
|
Something to keep in mind during implementation is that because listIndexes relies on the targeted shard owning chunks, we may need to start sending it with a shard version to be sure the router's targeting info wasn't stale. |