[SERVER-37595] [3.6] Handle WT_TRY_SALVAGE error code gracefully Created: 12/Oct/18  Updated: 29/Oct/23  Resolved: 01/Nov/18

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

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt End to End
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-10-22, Storage NYC 2018-11-05
Participants:

 Description   

With the backport of the 4.0 WiredTiger branch to 3.6, we need to gracefully handle the new error code that will be introduced. 

We should print out an error message with a dochub link to run --repair using a 4.0 binary.



 Comments   
Comment by Luke Chen [ 01/Nov/18 ]

louis.williams I just merged this ticket to v3.6 right after the  WT drop commit. I leave to you to resolve the CR and this ticket. 

Comment by Githook User [ 01/Nov/18 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-37595 [3.6] Handle WT_TRY_SALVAGE error code gracefully
Branch: v3.6
https://github.com/mongodb/mongo/commit/681588bf1a442979d5a4b32bc6f519428e2f3235

Comment by Luke Chen [ 15/Oct/18 ]

ian.whalen, you are right this needs to land together with the next 3.6 WT drop. As I understand this ticket needs new development work (i.e. point users to documentation in the error message, instead of backporting the original WT repair logic). Will assign it to louis.williams, who will work on the SERVER change and assign the ticket back to me once the change is done. I will then coordinate the code merge with the next 3.6 WT drop. 

Comment by Ian Whalen (Inactive) [ 12/Oct/18 ]

This should happen in conjunction with the next 3.6 drop.

Generated at Thu Feb 08 04:46:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.