[SERVER-55393] Fix stale_mongos_and_restarted_shards_agree_on_shard_version.js to exclude failed refreshes Created: 22/Mar/21  Updated: 29/Oct/23  Resolved: 24/Mar/21

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

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Sergi Mateo Bellido
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-04-05
Participants:
Linked BF Score: 131

 Description   

An assert of stale_mongos_and_restarted_shards_agree_on_shard_verion.js is checking how many full refreshes are done in a very specific scenario. The problem is that this test would like to check how many full refreshes were completed but what it is actually checking is how many full refreshes were started.

In order to fix that we could decrement the countFailedRefreshes counter. Nnote that this counter includes failed incremental AND failed full refreshes, but I think that for this case it is ok.



 Comments   
Comment by Githook User [ 24/Mar/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-55393 Fix stale_mongos_and_restarted_shards_agree_on_shard_version.js to exclude failed refreshes
Branch: master
https://github.com/mongodb/mongo/commit/7cfa7de2c1b8cefa90e0b6f4a24f13a0aa3c448a

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