[SERVER-31501] The `testMoveChunkWithSession` test utility should ensure the config server primary knows about the stepped-down shard Created: 10/Oct/17  Updated: 30/Oct/23  Resolved: 10/Oct/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.6.0-rc0

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-31184 Shard config.system.sessions Closed
Backwards Compatibility: Minor Change
Operating System: ALL
Sprint: Sharding 2017-10-23
Participants:

 Description   

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 :



 Comments   
Comment by Githook User [ 10/Oct/17 ]

Author:

{'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}

Message: SERVER-31501 In `testMoveChunkWithSession` ensure the config server primary knows about the stepped-down shard
Branch: master
https://github.com/mongodb/mongo/commit/0ef1d6ec05798f3dae9b838ad8a8fffdd7ec4990

Generated at Thu Feb 08 04:27:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.