[SERVER-72789] Validate the database/shard versions for bulkWrite sent from mongos Created: 12/Jan/23 Updated: 29/Oct/23 Resolved: 04/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Vishnu Kaushik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Repl 2023-03-06, Repl 2023-03-20, Repl 2023-04-03, Repl 2023-04-17 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently, database/shard version checks are done with the help of the OperationShardingState class. OperationShardingState already supports storing versions for multiple namespaces (despite the stale comment). So we will need to setShardRole as part of the command invocation based on the database/shard versions for the namespaces in the nsInfo before actually executing any operation. To do that, each entry in nsInfo may accept an unstable databaseVersion/shardVersion field used internally for router to shard database/shard version check for that namespace. |
| Comments |
| Comment by Githook User [ 03/Apr/23 ] |
|
Author: {'name': 'kauboy26', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: |