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

Don't drop the buckets collection in $out destructor only if there is a time-series collection

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration

      SERVER-91248 described a bug that affects concurrent view and collection creation in $out. If a view or collection is created while $out is happening, the destructor can't clean up the buckets collection (after it has been renamed) because of logic in dropCollection. However, we decided to fix that bug with two separate tickets (SERVER-92271 and SERVER-90862) that would prevent any concurrent view/collection being created or a rename to succeed if the namespaces conflict.

      Since these tickets are not completed we implemented a more conservative check in $out destructor in SERVER-90720. We only drop the buckets collection if we don't have a collection or view in the conflicting namespace.

      This ticket is to update $out testing and verify that the tickets above fix $out concurrent view/collection creation with time-series collections.

            Assignee:
            Unassigned Unassigned
            Reporter:
            gil.alon@mongodb.com Gil Alon
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: