[SERVER-62652] Balancer defragmentation test should check remaining chunks at the end of tests Created: 14/Jan/22  Updated: 29/Oct/23  Resolved: 08/Feb/22

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

Type: Task Priority: Major - P3
Reporter: Allison Easton Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-02-07, Sharding EMEA 2022-02-21
Participants:

 Description   

Currently, the test for defragmentation (balancer_defragmentation_merge_chunks.js) is testing that defragmentation has happened solely based on the number of chunks. This is not a very robust or thorough and should be replaced by checks on the chunks existing after the tests run.

After phase 1, we should ensure that there are no sequential chunks on the same shard. In phase 2, we can check that there are no small chunks left who could be merged with another chunk. And for phase 3, we should check that there are no chunks over the configured maxChunkSize.



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

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-62652 Balancer defragmentation test should check remaining chunks at the end of tests
Branch: master
https://github.com/mongodb/mongo/commit/93af3393c758bfb0e36c2c8453813968c028417f

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