Investigate whether to change or deprecate router's `splitVector` command

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2024-01-22
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      Router's splitVector command is only working for unsharded collections and targets the db primary assuming that the unsharded collections can only be hosted on it.

      This ticket is to decide what to do with such command considering that:

      • The assumption that only the primary shard is hosting unsharded collections will soon not hold anymore (SERVER-80136).
      • The splitVector implementation has always been flawed (SERVER-55028) and all internal usages have been replaced with autoSplitVector.

            Assignee:
            Unassigned
            Reporter:
            Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: