[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: |
|
||||||||||||||||
| 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: |