[SERVER-47068] Remove repair lock file when WT salvage refused to work on incompatible data files Created: 24/Mar/20  Updated: 29/Oct/23  Resolved: 02/Apr/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on WT-5630 Adding stage to turtle init to preven... Closed
Duplicate
is duplicated by WT-5776 Multiversion tests failing due to dat... Closed
Problem/Incident
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Execution Team 2020-04-06
Participants:
Linked BF Score: 95

 Description   

MongoDB 4.4 will refuse to start up on MongoDB 4.0 and earlier data files. When MongoDB 4.4 is run with --repair against 4.0 files, it will attempt to perform a salvage, but fail. In the case salvage fails because of a version incompatibility, no writes have been performed. In that case, the repair lock file should be removed, allowing MongoDB 4.0 to restart on those data files.



 Comments   
Comment by Githook User [ 02/Apr/20 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: SERVER-47006: Implement a downgrade floor between 4.4 and 4.2 SERVER-47068: Remove repair lock file when WT salvage refused to work on incompatible data files.
Branch: master
https://github.com/mongodb/mongo/commit/907fc7a809ae947f24395033027c68de9c7ae415

Comment by Githook User [ 30/Mar/20 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: SERVER-47068: Remove repair lock file when WT salvage refused to work on incompatible data files.
Branch: v4.4
https://github.com/mongodb/mongo/commit/d3be31346649750f991e4185e270acdda0667a22

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