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

The type of the "bits" field can differ between createIndexes and listIndexes

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • ALL
    • 34

      The createIndexes command doesn't specify a type for the "bits" field that is part of the index spec - though there is a struct type "NewIndexSpec" that does define a type for the bits field, the createIndexes command does not use it. However, the listIndexes command does define the "bits" field as type safeInt. This can lead to a problem during any collection cloning phase (we saw an error during Tenant Migrations, but it could happen during initial sync as well), because the node that is cloning indexes typically runs the listIndexes command to learn what indexes it should create.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            janna.golden@mongodb.com Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: