[SERVER-30404] movePrimary should take the same (dist)lock as shardCollection to ensure UUID consistency Created: 28/Jul/17 Updated: 30/Oct/23 Resolved: 19/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.10 |
| Fix Version/s: | 3.5.13 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Hugh Han |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Minor Change |
| Operating System: | ALL |
| Sprint: | Sharding 2017-07-31, Sharding 2017-08-21, Sharding 2017-09-11 |
| Participants: |
| Description |
|
movePrimary changes the collection's UUID, since it clones the collection to the new primary shard. if shardCollection is called concurrently, it may persist the original collection's UUID on the config server, leaving the UUIDs inconsistent between the cloned collection and the config server. |
| Comments |
| Comment by Githook User [ 22/Aug/17 ] |
|
Author: {'username': 'hughhan1', 'email': 'hughhan1@gmail.com', 'name': 'Hugh Han'}Message: |
| Comment by Githook User [ 19/Aug/17 ] |
|
Author: {'username': 'hughhan1', 'email': 'hughhan1@gmail.com', 'name': 'Hugh Han'}Message: |
| Comment by Esha Maharishi (Inactive) [ 28/Jul/17 ] |
|
Marked as "minor" backwards-breaking change, since it prevents movePrimary and shardCollection from running concurrently. |