[SERVER-55762] secondaryDelaySecs upgrade FCV checks don't work when 4.9 becomes last-continuous Created: 02/Apr/21  Updated: 29/Oct/23  Resolved: 06/Apr/21

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

Type: Bug Priority: Major - P3
Reporter: Pavithra Vetriselvan Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-55715 delay_secs_field_changes_on_upgrade_d... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.9
Sprint: Repl 2021-04-19
Participants:
Linked BF Score: 135

 Description   

This was discovered as fallout from SERVER-54434, which caused a few secondaryDelaySecs upgrade/downgrade tests to fail.

Checks like this use kLatest when allowing secondaryDelaySecs. However, once kLatest becomes 5.0, those checks will incorrectly exclude 4.9. We need to make sure the upgrade/downgrade and reconfig paths for the delay field name work as expected when 4.9 becomes last-continuous.

This is specifically an issue for upgrading shardsvrs from 4.4 to 4.9 and for downgrading shardsvrs from 5.0 to 4.9 where 4.9 is last-continuous and 5.0 is latest.



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

Author:

{'name': 'Pavi Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com', 'username': 'pvselvan'}

Message: SERVER-55762 Fix secondaryDelaySecs upgrade FCV checks when 4.9 becomes last-continuous

(cherry picked from commit 73721271e736cc97d30cf2fa177a2f53884b82f6)
Branch: master
https://github.com/mongodb/mongo/commit/6bc87d6324342fa96909f550f56c27e925e2dc1f

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