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

Investigate if it is safe to set unsharded collection metadata in opObserver

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2024-09-30, CAR Team 2024-10-14, CAR Team 2024-10-28, CAR Team 2024-11-11, CAR Team 2024-11-25

      We have two cases (1, 2)in which the ShardServerOpObserver set the unsharded collection metadata. It is not clear to me which guarantees do we have in the opObserver around the fact that those collections are actually unsharded.

      For instance in (1) do we really haveĀ  the guarantee that we can't create a sharded temporary collection or that we will not create/shard the temporary collections after its creation?

            Assignee:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: