[SERVER-64035] Some UNSHARDED router paths do not attach DB version Created: 28/Feb/22 Updated: 29/Oct/23 Resolved: 01/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2144-Milestone-0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
There are certain code paths which lead to buildUnshardedRequestsForAllShards with the expectation that this call will attach the UNSHARDED version to the collection. However, because [{{appendShardVersion}}|] doesn't modify its input parameter, they end up without the UNSHARDED version attached and appear to the shards as if they come from a direct connection. This violates the sharding protocol and may lead to bugs that are hard to predict or diagnose. |
| Comments |
| Comment by Githook User [ 01/Mar/22 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |