[SERVER-68485] Merge and Split commands should not use the CSR to check the shard version Created: 02/Aug/22 Updated: 29/Oct/23 Resolved: 12/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding EMEA 2022-08-08, Sharding EMEA 2022-08-22 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, the merge and split commands to the shards attach the shard version and therefore are checking the shard version is up to date with the CSR. Because merge and split are considered ddl operations, they should not do this. Instead, we should do checks similar to those done in move chunk/range which check that the chunks match what the command expects and returns StaleShardVersion otherwise |
| Comments |
| Comment by Githook User [ 12/Aug/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |