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

Create collection with dataShard might generate unreachable collections

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL

      Similarly to SERVER-86593 if the dataShard parameter is specified when trying to create an unsplittable collection, and we use the shard URL instead of the shard name, the create collection coordinator will commit the collection metadata in the config server, but the collection will be unreachable from the cluster. You can find a reproducible attached to the ticket.

      We should use something similar to move primary to ensure the proper shard id is selected.

            Assignee:
            Unassigned Unassigned
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: