[SERVER-71399] Jumbo chunk flag isn't automatically cleared after a chunk split Created: 16/Nov/22 Updated: 29/Oct/23 Resolved: 10/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.15, 6.0.4, 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Silvia Surroca | Assignee: | Silvia Surroca |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v6.2, v6.0, v5.0, v4.4, v4.2
|
||||||||||||
| Sprint: | Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Regading the MongoDB documentation about jumbo chunks, MongoDB removes the jumbo flag upon successful split of the chunk. That's not the actual behaviour, though. The current behaviour is that after a successful split of a jumbo chunk we get 2 new jumbo chunks because new chunks are initialised as a copy of the original chunk. Since there is no test controlling that, the scope of this ticket should also include a test case to cover that scenario. |
| Comments |
| Comment by Githook User [ 13/Jan/23 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: (cherry picked from commit fb8f9ecd5e32272c8c16101640f394a7621a6a82) |
| Comment by Githook User [ 11/Jan/23 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: (cherry picked from commit fb8f9ecd5e32272c8c16101640f394a7621a6a82) |
| Comment by Githook User [ 10/Jan/23 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |