[SERVER-76489] movePrimary set wrong collection version on new primary shard Created: 25/Apr/23 Updated: 29/Oct/23 Resolved: 08/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.24, 7.0.0-rc0, 6.0.5, 5.0.17, 4.4.21 |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc1, 6.0.7 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Tommaso Tocci | Assignee: | Sergi Mateo Bellido |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||||||
| Steps To Reproduce: | Originally tested version: r7.1.0-alpha-308-g9ec63c2a6fd Run the following test with:
|
||||||||||||||||
| Sprint: | Sharding EMEA 2023-05-01, Sharding EMEA 2023-05-15 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 150 | ||||||||||||||||
| Description |
|
MovePrimary creates collections on the new primary and set the shard version to UNSHARDED even if the collection is actually sharded. |
| Comments |
| Comment by Githook User [ 16/Jun/23 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: (cherry picked from commit 73013a50d60d58c9525df3e1e5b3c6ace21cb7f6) |
| Comment by Githook User [ 10/May/23 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: (cherry picked from commit 73013a50d60d58c9525df3e1e5b3c6ace21cb7f6) |
| Comment by Githook User [ 08/May/23 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |