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

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.1, 3.7.1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • v3.6
    • Sharding 2017-12-18
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None 

      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.

              Assignee:
              Jack Mulrow
              Reporter:
              Dianna Hohensee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: