[SERVER-73313] Ignore fixed dbVersions in ScopedSetShardRole Created: 25/Jan/23 Updated: 29/Oct/23 Resolved: 31/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding NYC 2023-02-06 |
| Participants: |
| Description |
|
ScopedSetShardRole will take a dbVersion for the database being accessed while its in scope, and install it on the OperationShardingState of its given opCtx. If the dbVersion is "fixed," it should be ignored since fixed versions are only used for the config and admin databases, which don't have real database metadata, since they must always be owned by the config server. Ignoring these versions matches how remote commands won't include a fixed dbVersion. This can be hit when a config server is acting as a shard when a shard component tries to read from a config db collection. |
| Comments |
| Comment by Githook User [ 30/Jan/23 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |