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

Ignore ConflictingOperationInProgress in random_moveChunk_update_shard_key_kill_sessions.js

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Cluster Scalability
    • 0

    Description

      See the linked BF for more details, but an update using the non internal transaction implementation that changes a document's shard key value and is retried on an Interruption error can fail with ConflictingOperationInProgress because a mongos already "started" tracking a transaction with the update's txnNumber. This test retries on interruption errors since it expects them, but in practice a driver won't retry on them, so a test only fix to ignore ConflictingOperationInProgress seems appropriate.

      Attachments

        Activity

          People

            backlog-server-cluster-scalability Backlog - Cluster Scalability
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: