[SERVER-45935] [3.6] WT error handler incorrectly prints "An unsupported journal format detected" Created: 03/Feb/20  Updated: 29/Oct/23  Resolved: 26/Feb/20

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

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

Issue Links:
Problem/Incident
is caused by SERVER-35271 4.0 rc0 upgrade from 3.6.5 logs "unsu... Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-02-24, Execution Team 2020-03-09
Participants:
Case:

 Description   

The logic in the WT error handler in MongoDB is the inverse of what it should be.

We evaluate if StringData::find() returns non-zero. Instead we should evaluate that it is not equal to std::string::npos, or -1.

This can confusingly report "An unsupported journal format detected" for all unrelated WiredTiger errors, except for the error it intends on detecting.

This was caused by a backport of SERVER-35271.



 Comments   
Comment by Githook User [ 26/Feb/20 ]

Author:

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

Message: SERVER-45935 WT error handler can incorrectly print 'An unsupported journal format detected'
Branch: v3.6
https://github.com/mongodb/mongo/commit/0df06232295d40295d874fe97fd532f107b4557f

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