[SERVER-41667] Disable 'wt_repair_corrupt_metadata.js' on debug builds Created: 12/Jun/19 Updated: 29/Oct/23 Resolved: 13/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0-rc2, 4.3.1 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Keith Bostic (Inactive) | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||||||
| Steps To Reproduce: | The related BF-13542 test failure is currently reliable and I would expect it to continue failing. |
||||||||||||||||
| Sprint: | Execution Team 2019-06-17 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 50 | ||||||||||||||||
| Description |
|
Reviewing the wt_repair_corrupt_metadata.js test, it's corrupting the database (by copying in a turtle that doesn't match the other files), and then asserting repair succeeds. When the turtle file doesn't match the other files, there's no reason to believe it will be possible to read the blocks in the WiredTiger.wt file referenced by the turtle file's checkpoints, and not being able to read a block is normally a fatal error in the WiredTiger library. Because this is a #HAVE_DIAGNOSTIC WiredTiger build, WiredTiger aborts and drops core. Here's the core dump stack trace:
I believe this is a test issue. There's no reason to believe a turtle or WiredTiger.wt file that doesn't match the rest of the database files can be used, any error you can imagine is possible and there are no operations that can be safely or reliably attempted. The storage group recently removed some WiredTiger standalone testing that attempted similar operations as part of |
| Comments |
| Comment by Githook User [ 13/Jun/19 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit 2581b5d745009e17ac5a94ea7fe1e9a41b7905ed) |
| Comment by Githook User [ 13/Jun/19 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Brian Lane [ 13/Jun/19 ] |
|
Thanks louis.williams for the writeup. FYI - milkie can we get the suggested changes in ASAP as luke.chen is currently blocked doing a WT drop for master and 4.2. Cheers! -Brian |
| Comment by Louis Williams [ 12/Jun/19 ] |
|
At the moment, this is only failing on debug builds because WT diagnostic mode is enabled. This test also depends on WT behavior that isn't guaranteed. I discussed with Keith and I think we should do the following for now:
If this test becomes more unreliable due to future changes, because we test something of which WT makes no guarantees, we can reevaluate the necessity of this test again. |