[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: |
|
||||||||||||
| 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 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: (cherry picked from commit 73721271e736cc97d30cf2fa177a2f53884b82f6) |