Replace CollectionRouter with DbPrimaryRouter in cluster::createCollectionWithRouterLoop

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The router loop in cluster::createCollectionWithRouterLoop currently has to be a CollectionRouter due to the old (non-shardsvr) create path potentially throwing staleConfig rather than StaleDBVersion.

      Once all creation paths go through the shardsvr create path, this can be changed to a dbPrimaryRouter.

            Assignee:
            Unassigned
            Reporter:
            Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: