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

Missed part of command response error in MigrationManager that should be checked with Shard::shouldErrorBePropagated()

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.4.0-rc2
    • Fix Version/s: 3.4.0-rc4
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2016-11-21

      Description

      The MigrationManager uses Shard::shouldErrorBePropagated on remote moveChunk command responses to check for errors that should not propagated back to another server. While the existing code checks the command execution errors from RemoteCommandResponse.data, it does not check any errors in sending the command, which are in RemoteCommandResponse.status. This was an oversight. All errors resulting from the remote command should be checked, sending as well as execution, before propagation back to another server.

      Uncheck point: https://github.com/mongodb/mongo/commit/53efde3280dd6a880987150777f5a26143df59e1#diff-7ff1485b59b3f10b5aa430f42e785635R764

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: