[SERVER-84090] Investigate whether to change or deprecate router's `splitVector` command Created: 12/Dec/23  Updated: 02/Feb/24  Resolved: 02/Feb/24

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Backlog - Catalog and Routing
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-84469 splitVector should not target using U... In Code Review
Related
related to SERVER-86171 Complete TODO listed in SERVER-84090 Needs Scheduling
Assigned Teams:
Catalog and Routing
Sprint: CAR Team 2024-01-22
Participants:

 Description   

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 that only exposes a shard command.

Generated at Thu Feb 08 06:54:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.