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

A migration will simply report "Data transfer error" when we have rich error details on the destination shard that are logged but not returned to the user

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.1, 3.7.1
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.6
    • Sprint:
      Sharding 2017-12-18

      Description

      moveChunk res: {
      		 
      	"ok" : 0,
      		 
      	"errmsg" : "Data transfer error",
      		 
      	"code" : 96,
      		 
      	"codeName" : "OperationFailed",
      		 
      	"$clusterTime" : {
      		 
      		"clusterTime" : Timestamp(1510773890, 3),
      		 
      		"signature" : {
      		 
      			"hash" : BinData(0,"KrDR/Iuwg3eUkgFxgvH9NTilYmk="),
      		 
      			"keyId" : NumberLong("6488724371891290116")
      		 
      		}
      		 
      }

      Wherever we call MigrationDestinationManager::setStateFailWarn, we're logging detailed error messages on the destination shard, but not returning the error messages.

      No logic issue, but usability issue.

        Attachments

          Activity

            People

            Assignee:
            jack.mulrow Jack Mulrow
            Reporter:
            dianna.hohensee Dianna Hohensee
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: