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

Chunk migration can unnecessarily fail due to inconsistency between listIndexes and local catalog

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 8.0.0
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2024-11-25
    • 2

      The listIndexes command uses different data types for some number fields (e.g. "bits") than what is stored on disk, which can lose precision. The migration recipient currently uses listIndexes to get the indexes the donor has for the collection. This can lead to indexes across shards having slightly different values if the migration would cause the index to be created, or it can lead to unnecessarily failing a migration if an index exists on both shards (because the value for some field but have lost precision and would not compare the same).

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            janna.golden@mongodb.com Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: