[SERVER-57182] reshardCollection command is shuffling data even when requested shard key already matches Created: 25/May/21 Updated: 29/Oct/23 Resolved: 10/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc2, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M3, PM-234-T-lifecycle, post-rc0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v5.0
|
||||||||
| Sprint: | Sharding 2021-06-14, Sharding 2021-05-31 | ||||||||
| Participants: | |||||||||
| Story Points: | 1 | ||||||||
| Description |
|
The reshardCollection command should instead return {ok: 1} without migrating any data when the request shard key pattern already matches the current one. The reshardCollection command is a long-running operation and the client's connection may get disconnected. It is important for the reshardCollection command to be manually retried by the client without causing a new instance of resharding the collection to occur had the earlier instance already completed. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 15/Jun/21 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: (cherry picked from commit df3f17d4ae56f4d22304498405fb072d9627f14a) |
| Comment by Githook User [ 10/Jun/21 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |