[SERVER-62959] Apply the right maxChunkSize value when migrating a chunk Created: 25/Jan/22  Updated: 29/Oct/23  Resolved: 02/Feb/22

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

Type: Bug Priority: Major - P3
Reporter: Paolo Polato Assignee: Paolo Polato
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2022-02-07
Participants:

 Description   

The chunk size for a specific collection is defined according to the following rules hierarchy:

  1. The collection specific chunk size maxChunkSizeBytes field in config.collection if set
  2. The global chunk size setting in config.settings.chunkSize if set
  3. The default global chunk size setting

Nevertheless, such criteria aren't respected when a chunk is being migrated out of a shard (more specifically, the wrong value may be taken into consideration when the "end of the catch up phase" condition is evaluated).



 Comments   
Comment by Githook User [ 02/Feb/22 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-62959 Apply the right maxChunkSize value when migrating a chunk
Branch: master
https://github.com/mongodb/mongo/commit/bd2f6813b9d499d75ceb26209935ba759764e493

Generated at Thu Feb 08 05:56:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.