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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2019-12-30
    • 23
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Cheahuychou Mao
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: