[SERVER-38149] Check if collection is sharded rather than checking for chunkManager Created: 15/Nov/18 Updated: 27/Oct/23 Resolved: 13/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | LamontN, pm-1051-legacy-tickets | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Sprint: | Sharding 2018-11-19 |
| Participants: |
| Description |
|
Since unsharded collections will now have a chunkManager, we cannot rely on checking the CachedCollectionRoutingInfo for a chunkManger to determine whether a collection is sharded or not in determining targeting for commands. We instead need to call the new isSharded() function. This needs to be changed in various parts of the code including but not limited to chunk_manager_targeter.cpp and many cluster_*.cpp files. |
| Comments |
| Comment by Tommaso Tocci [ 13/Dec/22 ] |
|
Generally commands are routed either to the primary shard of the database or using the scatter/gather helper function. Thus we believe this is not an issue anymore in recent versions. janna.golden@mongodb.com feel free to re-open the ticket if you think we still have a problem in master. |