[SERVER-47148] A stepdown might make the test stale_mongos_and_restarted_shards_agree_on_shard_version.js to fail Created: 27/Mar/20  Updated: 27/Oct/23  Resolved: 04/Mar/21

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

Type: Bug Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
Resolution: Gone away Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Steps To Reproduce:

Run the stale_mongos_and_restarted_shards_agree_on_shard_version.js test several times with the sharding_csrs_continuous_config_stepdown test suite.

Participants:
Linked BF Score: 12

 Description   

The test requires a stale router so any operation performed on a newly restarted shard triggers the behavior described on SERVER-32198. This way any fix of the PM-1645 project can be checked as they're committed. The sharding_csrs_continuous_config_stepdown test suite generates stepdowns, so when the stale router detects a change on the topology, among other operations, invalidates the database cache and refreshes the metadata, bringing it up to date. If this happens before any of the tested operations, it will make the operation to work as designed, and the assertions added to the test to detect the SERVER-32198 behavior will fail. 



 Comments   
Comment by Marcos José Grillo Ramirez [ 04/Mar/21 ]

Fixed by SERVER-47473.

Generated at Thu Feb 08 05:13:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.