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

updates_to_rangedeletions_collection_trigger_range_deletions.js should wait for deletions to complete before inserting orphans

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.3
    • Affects Version/s: 4.3.2
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Service Arch 2019-12-16
    • 16

      This test creates two shards with a chunk in each one. It then inserts documents to both and inserts some orphans directly to one of the shards. However, the initial moveChunk command will queue the chunk for deletion on the first shard asynchronously and may not run until after the orphans are inserted causing them to be deleted too early. 

      The test should use _waitForDelete in the moveChunk call. We should also review all of the related range deletion tests to see if this fix is needed there as well.

            Assignee:
            alex.taskov@mongodb.com Alexander Taskov (Inactive)
            Reporter:
            alex.taskov@mongodb.com Alexander Taskov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: