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

Do not emit error logs for self-recovering scenarios in BalancerStatsRegistry

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 6.0.16, 7.3.3, 8.0.0-rc5, 7.0.11
    • Affects Version/s: 6.0.0, 7.0.0, 8.0.0-rc0, 7.3.0
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v8.0, v7.3, v7.0, v6.0
    • CAR Team 2024-04-29, CAR Team 2024-05-13
    • 1

      Starting from v6.0, each range deletion document has a numOrphanDocs field that tells the approximate number of orphaned documents falling into a range. That counter can be incorrect in several contexts: in case of direct writes, while a range deletion is running (because the count goes down after deleting a batch) or during a migration (because the counter goes up after inserting* a batch and may not be updated in case of errors while cloning).

      That's a best effort counter that most of the times is correct and is used to approximately tell the balancer how much data for a given collection are orphaned. Worst case scenario when the count is wrong: some more/less data are moved around, not a big deal.

      This comment is incomplete and emitting an error here and here for a totally manageable scenario is too much.

      SERVER-75299 already reduced the severity of some log lines in the file, we should do that also for the two log lines linked above.

            Assignee:
            aitor.esteve@mongodb.com Aitor Esteve Alvarado
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: