Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-73537

`autoSplitVector` must not return invalid split points

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • Cluster Scalability Priorities

      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.

            Assignee:
            Unassigned Unassigned
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: