Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-67171

insert_with_data_size_aware_balancing.js fail: returning balancerComplaint as true when chunks are not fully balanced because orphanedCount is stale

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • ALL
    • Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25, Sharding EMEA 2022-08-08
    • 11

      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.

            silvia.surroca@mongodb.com Silvia Surroca
            silvia.surroca@mongodb.com Silvia Surroca
            0 Vote for this issue
            2 Start watching this issue