The testMoveChunkWithSession utility calls moveChunk right after it has stepped-down the primary of the donor shard.
As a result it is possible that the config server primary (which hosts the balancer) hasn't yet figured out the new shard replica set state and as a result the moveChunk command might fail with this message:
Error: command failed: {
"ok" : 0,
"errmsg" : "moveChunk command failed on source shard. :: caused by :: NotMaster: not master",
"code" : 96,
"codeName" : "OperationFailed"
} : undefined :
- is depended on by
-
SERVER-31184 Shard config.system.sessions
-
- Closed
-