[SERVER-74214] Cannot downgrade from fresh 6.2 due to oplog cap size Created: 21/Feb/23  Updated: 29/Oct/23  Resolved: 25/Mar/23

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

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Matt Kneiser
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Documented
is documented by DOCS-15986 Investigate changes in SERVER-74214: ... Closed
Problem/Incident
is caused by SERVER-67246 Remove size multiple restriction on c... Closed
Related
Assigned Teams:
Storage Execution
Backwards Compatibility: Minor Change
Operating System: ALL
Backport Requested:
v6.3, v6.2
Sprint: Execution Team 2023-04-03
Participants:

 Description   

SERVER-67246 unlocked the ability for the oplog capped size to be anything, not just a multiple of 256. This blocks fresh installs from downgrading.
I think we should fix this by adjusting the oplog cap size algorithm to go back to rounding to the nearest 256. This will avoid problems with on-prem LTS users on 7.0 downgrading to 6.0.



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

Author:

{'name': 'Matt Kneiser', 'email': 'matt.kneiser@mongodb.com', 'username': 'themattman'}

Message: SERVER-74214 New oplog size should be a multiple of 256 for back-compat
Branch: master
https://github.com/mongodb/mongo/commit/56d9c847ef0b81902c80c3f8aa4c921049f02a43

Comment by Connie Chen [ 23/Feb/23 ]

We should aim to complete this before 7.0, at triage we should assign the 7.0 required fixversion

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