[SERVER-67171] insert_with_data_size_aware_balancing.js fail: returning balancerComplaint as true when chunks are not fully balanced because orphanedCount is stale Created: 10/Jun/22  Updated: 29/Oct/23  Resolved: 27/Jul/22

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

Type: Bug Priority: Major - P3
Reporter: Silvia Surroca Assignee: Silvia Surroca
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-67301 Balancer may perform one unnecessary ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25, Sharding EMEA 2022-08-08
Participants:
Linked BF Score: 11

 Description   

Some failures have been observed in insert_with_data_size_aware_balancing.js because the balancerCollectionStatus command is returning a balancerComplaint as true when data are not already fairly balanced because numOrphanDocs is read by the balancer while it's stale.

The detailed explanation of why is this happening can be found in the description of SERVER-66835.

A fix suggestion would be to change the test and wait a few more balancer rounds after the balancerComplaint returns true. Another option is to update the numOrphanDocs variable at the same time the range deleter deletes the orphan chunks to avoid stale reads.



 Comments   
Comment by Silvia Surroca [ 27/Jul/22 ]

Fix commited under ticker SERVER-67301

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