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

Investigate if there are other operations that may not persist config time after a collection drop at migration_util.cpp

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When we are sure that all operations persist the config time after a drop collection, we can remove this extra "waitForDurableConfigTime".

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: