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

Timeseries inserts may fail with NamespaceNotFound after moveCollection

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: 7.0.0, 8.0.0-rc0, 7.3.0, 8.1.0-rc0
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0, v7.0
    • Hide

      Repro attached

      Show
      Repro attached
    • CAR Team 2024-07-08, CAR Team 2024-07-22, CAR Team 2024-08-05, CAR Team 2024-08-19, CAR Team 2024-09-02
    • 0

      The timeseries insert path checks for the presence of the bucket collection before acquiring the collection and checking the shard version. This is because the timeseries bucket options are needed for inserting into the in memory bucket catalog, but the collection locks are not needed at this point (because nothing persisted is being done yet).

      In the case that a moveCollection happened, the bucket collection may no longer exist and so we will return NamespaceNotFound at the first check rather than throwing staleConfig at the later check.

            Assignee:
            robert.sander@mongodb.com Robert Sander
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: