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

Time series insert may return collection not found error

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • ALL
    • 200

      If the catalog state changes in certain ways during an insert command to a time series collection (e.g. collection is dropped, or we enter replication rollback), we may report an error to the user that the collection was not found. This is somewhat confusing behavior, as for normal collections we would implicitly create the collection. We should be able to handle this more transparently by adding some higher-level retry logic to restart the command when such a catalog change is detected.

            Assignee:
            Unassigned Unassigned
            Reporter:
            dan.larkin-york@mongodb.com Dan Larkin-York
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: