[SERVER-45944] disallow downgrade to 4.2 if there is an index build in progress Created: 04/Feb/20  Updated: 29/Oct/23  Resolved: 18/Feb/20

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

Type: Task Priority: Major - P3
Reporter: Sara Williamson Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-44468 Enable characterize_index_builds_on_r... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-02-24
Participants:
Linked BF Score: 38

 Description   

Two phase index builds are a 4.4-only feature. We should not allow a FCV downgrade to 4.2 if there are still index builds in progress. This avoids propagating a commitIndexBuild/abortIndexBuild oplog entry to the secondary node if the index builds completes after the FCV update is done.



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

Author:

{'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}

Message: SERVER-45944 disallow downgrade to 4.2 if there is an index build in progress
Branch: master
https://github.com/mongodb/mongo/commit/046a1a3f14c42dc52f1d83c9e2fdb6127783a8d6

Comment by Githook User [ 18/Feb/20 ]

Author:

{'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}

Message: SERVER-45944 add js test for fcv downgrade during index builds

create mode 100644 jstests/noPassthrough/index_downgrade_fcv.js
Branch: master
https://github.com/mongodb/mongo/commit/e01b8611919d8da6510818bf8a27e78e0c038418

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