[SERVER-34274] Extend database_and_shard_versioning_all_commands.js to also use movePrimary to make a client or server's databaseVersion stale Created: 03/Apr/18  Updated: 29/Oct/23  Resolved: 06/Apr/18

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

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-04-09
Participants:

 Description   

Currently, the database_and_shard_versioning_all_commands.js iterates through every command, and for commands that send databaseVersion, it checks that the shard's cached databaseVersion was refreshed as a result of the command being sent.

To make the shard's cached databaseVersion stale in between each command, the test drops the database from the shard.

This ticket is to extend the test to iterate through the commands a second time, but this time use movePrimary instead of dropDatabase. This should clear the shard's cached metadata (as part of the movePrimary critical section), so the next command with a databaseVersion should cause the shard to refresh and find the new databaseVersion.



 Comments   
Comment by Githook User [ 06/Apr/18 ]

Author:

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

Message: SERVER-34274 Extend database_and_shard_versioning_all_commands.js to also use movePrimary
to make a client or server's databaseVersion stale
Branch: master
https://github.com/mongodb/mongo/commit/1f88f3182f4e3f9054f1da71787f302efbd61836

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