[SERVER-82075] shard_role:acquireCollection can trip invariant when placementConcern has dbVersion but no shardVersion Created: 11/Oct/23 Updated: 29/Oct/23 Resolved: 16/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30 | ||||
| Participants: | |||||
| Linked BF Score: | 132 | ||||
| Description |
|
This invariant will be tripped if an operation calls `acquireCollection` with a placement concern that has a DatabaseVersion set, but no ShardVersion, and the collection is sharded. |
| Comments |
| Comment by Githook User [ 16/Oct/23 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |