[SERVER-65536] Relax constraints on numer of records in ShardsvrGetStatsForBalancingCmd Created: 13/Apr/22  Updated: 29/Oct/23  Resolved: 19/Apr/22

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

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
is duplicated by SERVER-65537 _shardsvrGetStatsForBalancing can inv... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.0
Sprint: Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02
Participants:

 Description   

Since range deletion tasks are not using transactions, it may happen that part of a batch gets deleted but the orphans count is not updated yet. This means that we can't expect that the number of records (at storage level) must always be greater than the number of orphans (tracked in range deletion task documents and updated asynchronously).

Purpose of this ticket is to relax this invariant and instead simply return 0 in case the number of records exceeds the number of orphaned documents.



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

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-65536 Relax constraints on numer of records in ShardsvrGetStatsForBalancingCmd

(cherry picked from commit 170f9451a7709410b6e2162c74bf60a56960f484)
Branch: v6.0
https://github.com/mongodb/mongo/commit/3c5383d382ff075143c1fe46e7599021cb84e67d

Comment by Githook User [ 19/Apr/22 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-65536 Relax constraints on numer of records in ShardsvrGetStatsForBalancingCmd
Branch: master
https://github.com/mongodb/mongo/commit/170f9451a7709410b6e2162c74bf60a56960f484

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