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

Chunk migration may fail due to indexes having not relevant and invalid index options

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: 6.0.0, 5.0.10, 7.0.0, 8.0.0-rc0
    • Component/s: Catalog, Sharding
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • Execution Team 2024-01-22, Execution Team 2024-02-05, Execution Team 2024-02-19, Execution Team 2024-08-05, CAR Team 2024-09-30
    • 2

      IndexCatalogImpl::removeExistingIndexesNoChecks() does not account for index_key_validate::repairIndexSpec() to remove invalid index options when it calls _doesSpecConflictWithExisting().

      {"s":"W",  "c":"SHARDING", "id":23777,   "ctx":"MoveChunk","msg":"Error while doing moveChunk","attr":{"error":"OperationFailed: Data transfer error: migrate failed: CannotCreateCollection: aborting, shard is missing 1 indexes and collection is not empty. Non-trivial index creation should be scheduled manually"}}
      

            Assignee:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: