[SERVER-73537] `autoSplitVector` must not return invalid split points Created: 02/Feb/23  Updated: 26/Oct/23

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

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

Issue Links:
Depends
depends on SERVER-12536 Only allow shard key types which can ... Backlog
Related
related to SERVER-73441 Make sure shard key bounds are valid ... Closed
related to SERVER-12536 Only allow shard key types which can ... Backlog
Assigned Teams:
Catalog and Routing
Participants:

 Description   

Before committing a migration this check is ensuring that the bounds are valid shard keys.

Given that moveRange is choosing a bound relying on the output of autoSplitVector, we should make sure that it never returns invalid split points. This will help to:

  • Avoid wasting time cloning before failing the commit
  • Avoid repeatedly selecting invalid split points

This ticket is an optimization that will not be needed in case SERVER-12536 gets done.


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