[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: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Execution Team 2020-02-24, Execution Team 2020-03-09 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| 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 |
| Comments |
| Comment by Githook User [ 26/Feb/20 ] |
|
Author: {'name': 'Louis Williams', 'username': 'louiswilliams', 'email': 'louis.williams@mongodb.com'}Message: |