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

Cannot assume the batch has been inserted when using failpoint tenantMigrationHangCollectionClonerAfterHandlingBatchResponse

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • Repl 2021-02-22
    • 13

    Description

      In test tenant_migration_resume_collection_cloner_after_rename.js, we use the failpoint tenantMigrationHangCollectionClonerAfterHandlingBatchResponse and assume that the documents cloned are inserted when the failpoint is hit. This may not be the case. This is because in the collection cloner, insertDocumentsCallback is called on a different thread. And hitting the failpoint tenantMigrationHangCollectionClonerAfterHandlingBatchResponse doesn't necessarily mean the insertDocumentsCallback has finished executing.

      So I think we need to change the jsTest to use assert.soon when checking the number of documents cloned.

      Attachments

        Activity

          People

            lingzhi.deng@mongodb.com Lingzhi Deng
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: