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

migration_util function may miss some response errors when submitting remote commands through sendToRecipient()

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.2.0, 4.4.11, 5.0.4, 5.1.0-rc2
    • Affects Version/s: 5.0.3, 4.4.9, 5.1.0-rc0
    • Component/s: None
    • Labels:
    • Fully Compatible
    • ALL
    • v5.1, v5.0, v4.4
    • Sharding EMEA 2021-10-18, Sharding EMEA 2021-11-01
    • 24

      In BFG-872835 it could be observed the following sequence:

      1. a chunk migration reaches the commit phase
      2. the migration coordinator issues a request for removing the related range deletion document
      3. the recipient steps down before deleting the document - supposedly returning an error
      4. sendToRecipient() should detect the remote error and raise an exception to interrupt the migration coordinator - but nothing happens.

      The root cause of this is considered to lie in the use of Shard::CommandResponse::getEffectiveStatus() for processing remote errors - for write operation requests getStatusFromWriteCommandReply() is generally preferred.

            paolo.polato@mongodb.com Paolo Polato
            paolo.polato@mongodb.com Paolo Polato
            0 Vote for this issue
            4 Start watching this issue