[SERVER-66048] CollectionPtr::isSharded() always returns false when connecting directly to the shard Created: 28/Apr/22 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Josef Ahmad | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | PM-2144-Milestone-0, oldshardingemea | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Possibly because the end client does not attach routing metadata with the request, unlike a mongos. |
| Comments |
| Comment by Jordi Serra Torrens [ 04/Jul/23 ] |
|
Until the shards are made authoritative for the sharding description/ownership metadata, this information can only be available to versioned requests (i.e. shardVersion attached). PM-2948 will make the shards authoritative, so we're moving this ticket to it. Additionally, PM-2689 forbids direct connections to shards, which means only "internal" operations can ever request the description on a shard without having passed through a router. |
| Comment by Kaloian Manassiev [ 04/May/22 ] |
|
Then I am moving it under PM-2144 and marking it as dependency of |
| Comment by Josef Ahmad [ 04/May/22 ] |
|
kaloian.manassiev@mongodb.com no hard dependency on my side as I've been able to work around it. |
| Comment by Kaloian Manassiev [ 04/May/22 ] |
|
We are pushing the state from the CSR down into the Collection object, so this will mimic the behaviour of the CSR eventually. However, it looks like the CSR has the same semantics for direct connections. I guess we will need to revisit that. josef.ahmad@mongodb.com, is this a blocker for something? |