[SERVER-26531] jumbo flag in chunk can be cleared when the shard that owns it donates a chunk Created: 07/Oct/16 Updated: 23/Sep/19 Resolved: 27/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.4.0-rc0, 3.4.21, 3.6.13, 4.0.10 |
| Fix Version/s: | 3.6.14, 4.0.11, 4.2.0-rc3, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 1 |
| Labels: | todo_in_code | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||
| Backport Requested: |
v4.2, v4.0, v3.6
|
||||||||||||||||||||||||||||
| Sprint: | Sharding 2019-07-01 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||
| Description |
|
During the commit phase of the migration, the moveChunk command will set the chunk being migrated with a new major version and selects a random chunk of the current shard to have the same major version. This is done using replacement update so if a chunk that gets selected is a jumbo chunk, the flag will get cleared inadvertently. Also uncomment this line in test after fixing: |
| Comments |
| Comment by Githook User [ 30/Jun/19 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: ... because having it return Status just so all callers can assert that (cherry picked from commit 4b955e6a1a35b1704a05aa29bd7e6ed42612333c) |
| Comment by Githook User [ 30/Jun/19 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: (cherry picked from commit 8fd79fe845e3e4717df26abb78c3fb7859f3823e) |
| Comment by Githook User [ 30/Jun/19 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: ... because having it return Status just so all callers can assert that (cherry picked from commit 4b955e6a1a35b1704a05aa29bd7e6ed42612333c) |
| Comment by Githook User [ 30/Jun/19 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: (cherry picked from commit 8fd79fe845e3e4717df26abb78c3fb7859f3823e) |
| Comment by Githook User [ 30/Jun/19 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: ... because having it return Status just so all callers can assert that (cherry picked from commit 4b955e6a1a35b1704a05aa29bd7e6ed42612333c) |
| Comment by Githook User [ 30/Jun/19 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: (cherry picked from commit 8fd79fe845e3e4717df26abb78c3fb7859f3823e) |
| Comment by Githook User [ 27/Jun/19 ] |
|
Author: {'name': 'Kaloian Manassiev', 'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com'}Message: ... because having it return Status just so all callers can assert that |
| Comment by Githook User [ 27/Jun/19 ] |
|
Author: {'name': 'Kaloian Manassiev', 'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com'}Message: |