[SERVER-48082] WT clean shutdown should do a quick exit before shouldDowngrade() check if the node is still not safe to take stable checkpoints. Created: 11/May/20  Updated: 29/Oct/23  Resolved: 15/May/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.7.0

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

Issue Links:
Depends
Related
related to SERVER-47219 Correct downgrade_after_rollback_via_... Closed
related to SERVER-38925 Rollback via refetch can cause _id du... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-05-18
Participants:
Linked BF Score: 50

 Description   

Currently, we would be able to take stable checkpoints when stable timestamp < initial data timestamp if the WT files needs to be downgraded on shutdown. This can result in data corruption (like SERVER-38925).

As part of this git commit hash (SERVER-47219), we moved the stable & initial data timestamp comparison check before downgrade check. Unfortunately, this fix is present only in 4.4. and not in master (> mongoDB 4.4 version).  This ticket would forward port only the C++ changes (and not test changes) present in this git commit.



 Comments   
Comment by Githook User [ 15/May/20 ]

Author:

{'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}

Message: SERVER-48082 WT clean shutdown should do a quick exit before shouldDowngrade() check if the node is not safe to take stable checkpoints. (cherry picked from commit0b9f132bd60875a276f3cdaa53efe5e5bb5d1f0b)
Branch: master
https://github.com/mongodb/mongo/commit/45b91db74d9ac18a3bad3189a6ae120e549dfa08

Comment by Suganthi Mani [ 11/May/20 ]

CC daniel.gottlieb

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