[SERVER-84469] splitVector should not target using UNSHARDED version Created: 02/Jan/24  Updated: 06/Feb/24

Status: In Code Review
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Enrico Golfieri Assignee: Enrico Golfieri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-84090 Investigate whether to change or depr... Closed
Assigned Teams:
Catalog and Routing
Operating System: ALL
Sprint: CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19
Participants:

 Description   

The command {splitVector ..} currently still targets the primary shard using UNSHARDED  version. This was ok before because the command is supposed to run only on unsharded collection. For the same reason, the command should now run against the unsplittable collection.

The goal of this ticket is to:

  • update the unsharded version with the correct shard version if the feature flag is enabled 
  • Remove this  check and replace it with a proper router loop ( always check the collection is still unsplittable at every attempt)
  • Refresh in case of input sharded nss and remove this assertion : After the introduction of the {unshardCollection .. } command, the information might be stale on the router. 

 

 


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