[SERVER-51430] update log message search in recovery_wt_cache_full.js to look at end of oplog application Created: 08/Oct/20 Updated: 29/Oct/23 Resolved: 08/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Execution Team 2020-10-19 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 37 | ||||||||||||||||||||||||||||
| Description |
|
This test was written to detect a log message at the start of the oplog application process during recovery. Since we have a bounded buffer for storing log messages for tests, the log message that we are looking for may no longer be around if the startup logs are too verbose. Instead, we can make the test more robust by checking the results at the end of the oplog application. |
| Comments |
| Comment by Githook User [ 08/Oct/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |