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

Direct shard connections warnings in single shard clusters may be emitted more than once

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2024-05-13, CAR Team 2024-05-27, CAR Team 2024-06-10, CAR Team 2024-06-24

      The direct shard connection checks are present in both AutoGetDB and AutoGetCollection. SERVER-86796 added the direct shard connection places in such a way that these checks may be repeated multiple times for certain operations (for example, the checks are present in both AutoGetDB and AutoGetCollection). This is to prevent a situation where the checks pass, then a second shard is added to the cluster and a collection is moved, and then the locks are acquired.

      When these checks throw errors, this is fine because the first failure will throw an error. For warnings, however, this means we can end up emitting multiple warnings for the same operation.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: