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

index_operations_abort_concurrent_outgoing_migrations.js shouldn't assert that the recipient doesn't have the index created on the donor

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.3
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2019-12-30
    • 23

    Description

      If a migration is aborted between _recvChunkStart and _migrateClone , the recipient might end up cloning indexes and options before it finds out that the migration has been aborted. So for the createIndexes tests, we should not assert that the recipient shard doesn't have the index created on the donor shard during migration.

      Attachments

        Activity

          People

            cheahuychou.mao@mongodb.com Cheahuychou Mao
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: