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

[test-only] Accept moveChunk failures waiting for the range deleter if refineCollectionShardKey is run concurrently in `random_moveChunk_refine_collection_shard_key.js`

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.1
    • Affects Version/s: 6.0.0, 7.0.0, 8.0.0-rc0, 7.3.0
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0, v7.0, v6.0
    • CAR Team 2024-09-02, CAR Team 2024-09-16, CAR Team 2024-09-30
    • 0

      The `random_moveChunk_refine_collection_shard_key.js` test concurrently runs moveChunk and refineCollectionShardKey, with the latter causing migrations to abort or be interrupted.

      The test infrastructure allows for some expected errors that won't cause the test to fail if the moveChunk fails due to the abortMigrations of the refineCollectionShardKey.

      If the abortMigrations interrupts when the moveChunk is waiting for the future of the range deleter to complete, the error is not accepted, and the test fails.

      The goal of this ticket is to make the test robust to this error.

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: