[SERVER-39180] Wrong initial chunk owner shard can be selected when sharding non-empty collection with pre-created zones Created: 24/Jan/19 Updated: 29/Oct/23 Resolved: 25/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.0.5 |
| Fix Version/s: | 4.0.6, 4.1.8 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | SWNA | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||
| Sprint: | Sharding 2019-01-28, Sharding 2019-02-11 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Issue Status as of Jan 30, 2019 ISSUE DESCRIPTION AND IMPACT DIAGNOSIS AND AFFECTED VERSIONS REMEDIATION AND WORKAROUNDS FIXED VERSIONS Original descriptionWhen sharding a non-empty collection, whose primary is not the first alphabetically-sorted shard, the Fast Initial Split logic can select wrong shard for the lone initial chunk. These are the conditions for this issue to occur:
In this case, attempting to shard such a collection will wrongly place the only chunk on the first alphabetically-sorted shard, which means none of the documents for that collection will be visible anymore. |
| Comments |
| Comment by Githook User [ 25/Jan/19 ] |
|
Author: {'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev'}Message: (cherry picked from commit ec3a2060a3fbdd8808a39533b25e6b270ea95b28) |
| Comment by Kaloian Manassiev [ 25/Jan/19 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}Message: |