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

Committing timeseries buckets can fail due to missing buckets collection

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2025-02-03, CAR Team 2025-02-17
    • 200

      SERVER-95650 has added checks ( 1, 2 ) inspecting the presence of the buckets collection to the commitTimeseriesBucket and commitTimeseriesBucketsAtomically methods in the timeries write path.
      These checks were introduced alongside a lookup of the buckets collection from the collection catalog, followed by the propagation of the associated default collator to the introduced prepareCommit function.

      However, this approach can lead to the buckets collection not being found when a concurrent operation transfers data of the given collection from shard A to shard B, and then drops that collection on the donor (after the insert has started but before the aforementioned code is reached). In this case a refresh due to a shard version mismatch would be expected instead.

        1. repro.patch
          5 kB

            Assignee:
            robert.sander@mongodb.com Robert Sander
            Reporter:
            robert.sander@mongodb.com Robert Sander
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: