[SERVER-63605] validate_tests fails after some WT changes Created: 14/Feb/22 Updated: 29/Oct/23 Resolved: 23/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0, 5.3.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Etienne Petrel | Assignee: | Jordi Olivares Provencio |
| 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: |
v5.3
|
||||||||||||||||||||||||||||
| Steps To Reproduce: |
|
||||||||||||||||||||||||||||
| Sprint: | Execution Team 2022-03-07 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 65 | ||||||||||||||||||||||||||||
| Description |
|
We recently merged
|
| Comments |
| Comment by Githook User [ 25/Feb/22 ] | ||
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: (cherry picked from commit 2fca2d4e19a642fd97374dfde65bc04799b73f58) | ||
| Comment by Githook User [ 23/Feb/22 ] | ||
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: | ||
| Comment by Luke Chen [ 23/Feb/22 ] | ||
|
As this ticket is a dependency of | ||
| Comment by Keith Bostic (Inactive) [ 22/Feb/22 ] | ||
|
Thank you, louis.williams. If you're OK changing the test to ignore those warnings, that would be great! | ||
| Comment by Louis Williams [ 22/Feb/22 ] | ||
|
The unit test failures appear to be caused by the test receiving more warnings from validate than expected. And this is due to the following warnings: "Could not complete validation of table:collection-306-6794401668041455030. This is a transient issue as the collection was actively in use by other operations." We return this as a warning when we get an EBUSY error validating the tables, so this is entirely expected. We can either change the tests to ignore these messages, or change validate to use the code Chenhao provided. The latter would probably be too consequential since we run validate frequently in testing, and these tests would probably take much longer to complete. | ||
| Comment by Keith Bostic (Inactive) [ 21/Feb/22 ] | ||
|
geert.bosch, louis.williams, could we get someone to take a fast look at The summary is we’re going to stop allowing operations like alter, or verify, that require exclusive access to files, to proceed if there is dirty data in the cache. We historically checkpointed the file to flush the dirty data from the cache to allow exclusive access, but that leads to data inconsistency as the history-store file is not checkpointed along with the file. cc: alexander.gorrod | ||
| Comment by Chenhao Qu [ 14/Feb/22 ] | ||
|
WiredTiger intends to disallow single file checkpoint in The code should look like:
| ||
| Comment by Etienne Petrel [ 14/Feb/22 ] | ||
|
geert.bosch, would your team be the right one to work on this ticket? chenhao.qu, can you provide more context about the intent of |