[SERVER-37074] Validation hook should continue downgrading if a downgrade was interrupted Created: 11/Sep/18  Updated: 29/Oct/23  Resolved: 30/Nov/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.1.6

Type: Bug Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: tig-dataconsistency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
causes SERVER-44613 ValidateCollections hook does not cal... Closed
Related
is related to SERVER-36718 Validation hook should upgrade before... Closed
is related to SERVER-43627 Remove v4.2 FCV handling from Validat... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: STM 2018-12-17
Participants:
Linked BF Score: 14
Story Points: 2

 Description   

SERVER-36718 made the changes so that we can use forceValidationWithFeatureCompatibilityVersion to upgrade the servers before validating the collections. But BF-10462 is a case when a downgrade in the test was interrupted and there is no way for the validation hook to start the upgrade in the middle of a downgrade. Therefore, the validation hook should first downgrade and then upgrade in this case.



 Comments   
Comment by Githook User [ 30/Nov/18 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-37074 Handle interrupted FCV downgrade in validate hook.
Branch: master
https://github.com/mongodb/mongo/commit/492493e2fc8162a1ee82fbc3ddf052a136670c75

Comment by Max Hirschhorn [ 18/Sep/18 ]

As part of this ticket it'd be good to run the data_consistency_checks.js test with TestData.forceValidationWithFeatureCompatibilityVersion set.

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