[SERVER-33196] add 'forTest' flag to movePrimary, and if it's set, make _configsvrMovePrimary call movePrimary on the primary shard Created: 08/Feb/18  Updated: 29/Oct/23  Resolved: 26/Feb/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.7.3

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-02-12, Sharding 2018-02-26, Sharding 2018-03-12
Participants:

 Description   

We want to be able to incrementally test the new movePrimary protocol as it's being developed, so let's add a temporary 'forTest' boolean flag to mongo's and the config server's movePrimary IDL definitions.

If the flag is set, configsvrMovePrimary should call movePrimary against the primary shard; otherwise, it should execute the existing movePrimary logic.

Add a jstest that calls movePrimary with the 'forTest' flag to ensure it's working.



 Comments   
Comment by Githook User [ 26/Feb/18 ]

Author:

{'email': 'blake.oler@mongodb.com', 'name': 'Blake Oler', 'username': 'BlakeIsBlake'}

Message: SERVER-33196 add 'forTest' flag to movePrimary, and if it's set, make _configsvrMovePrimary call movePrimary on the primary shard
Branch: master
https://github.com/mongodb/mongo/commit/c88d4b73a63011f624cc1cf1cdd7692943d11ffa

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