[SERVER-21931] Only mark chunks as jumbo if split fails because the chunk is too large Created: 17/Dec/15  Updated: 22/Apr/19  Resolved: 22/Apr/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.1.11

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Janna Golden
Resolution: Done Votes: 0
Labels: ShardingRoughEdges, high-value, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-13806 Need better detection and reporting o... Closed
related to SERVER-13024 Clear the 'jumbo' flag from the chunk... Blocked
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2019-04-22
Participants:

 Description   

Currently, if the balancer tries to move a chunk and fails because it is too large, it will then attempt to split that chunk. If the split fails for any reason we mark the chunk as jumbo. This means that things like transient network errors and the config servers not being available for writes can lead to chunks being marked as jumbo incorrectly. We should only mark the chunk as jumbo if the reason it failed to be split is that it is in fact jumbo.



 Comments   
Comment by Githook User [ 22/Apr/19 ]

Author:

{'name': 'jannaerin', 'username': 'jannaerin', 'email': 'golden.janna@gmail.com'}

Message: SERVER-21931 Only mark chunks as jumbo on CannotSplit errors
Branch: master
https://github.com/mongodb/mongo/commit/fbaa4f4e91534ebb2dffba33e3740e91d7782e22

Generated at Thu Feb 08 03:58:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.