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

Test `migration_fails_if_exists_in_rangedeletions.js` needs to increment timeout `receiveChunkWaitForRangeDeleterTimeoutMS`

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • None
    • None
    • Fully Compatible
    • ALL
    • Sharding EMEA 2022-09-05
    • 5

    Description

      We have observed occasionally failures in migration_fails_if_exists_in_rangedeletions.js due to host slowness.

      The reason is that the 
      receiveChunkWaitForRangeDeleterTimeoutMS has been increased only on shard1 (here) and not on shard0, which is the one that is actually performing the range deletion.
       
      As a suggestion I would consider to update the receiveChunkWaitForRangeDeleterTimeoutMS on the suite configuration instead of doing it locally per every test. This solution has already been applied for other suites like sharding_auth_audit, concurrency_sharded_multi_stmt_txn_with_balancer, etc.

      The suites affected on BF-25847 are sharding and sharding_opportunistic_secondary_targeting
       

      Attachments

        Activity

          People

            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            silvia.surroca@mongodb.com Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: