[SERVER-55209] Ensure safety parsing oplog entries from config.transactions after downgrading with retryable time-series inserts Created: 15/Mar/21  Updated: 29/Oct/23  Resolved: 19/Apr/21

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

Type: Task Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
is related to SERVER-56573 Ignore config.transactions entries re... Closed
is related to SERVER-56171 Remove time-series downgrade logic Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-04-19, Execution Team 2021-05-03
Participants:
Linked BF Score: 68

 Description   

A downgraded node could find an oplog entry containing multiple statement ids through the retryable write state persisted in this collection. To remedy this, one potential solution is on setFCV downgrade, we traverse through the config.transactions collection and remove any entries referencing a retryable time-series oplog entry. An alternative is to set a 4.4 downgrade floor, and to teach 4.4 to parse these new oplog entries.



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

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-55209 Remove entries from config.transactions that reference oplog entries from time-series inserts on FCV downgrade
Branch: master
https://github.com/mongodb/mongo/commit/8dd77768b7bbf74214b65ad14d8549246bc28d53

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