[SERVER-63758] Fix post-defragmentation checks Created: 17/Feb/22  Updated: 29/Oct/23  Resolved: 24/Feb/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0, 5.3.0-rc3

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

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.3
Sprint: Sharding EMEA 2022-02-21, Sharding EMEA 2022-03-07
Participants:

 Description   

There are some bugs in the post-defragmentation checks that are preventing us from catching problems with defragmentation. The main issue is that the util is comparing the shard key values with ===, but objects must use woCompare. Another is that the zone comparison is using assert.leq which does not exist in javascript, it should be lte



 Comments   
Comment by Githook User [ 04/Mar/22 ]

Author:

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

Message: SERVER-63758 Fix post-defragmentation checks
Branch: v5.3
https://github.com/mongodb/mongo/commit/6e9b39f474fe1cb58aae2d9791f1be726f73dbdb

Comment by Githook User [ 24/Feb/22 ]

Author:

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

Message: SERVER-63758 Fix post-defragmentation checks
Branch: master
https://github.com/mongodb/mongo/commit/3295c36b9ed0c5b14ec7e39876f1c994b2139ff8

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