[SERVER-68244] Investigate tiered logging in resmoke.py to insulate against LogKeeper DB performance Created: 23/Jul/22 Updated: 29/Oct/23 Resolved: 30/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Robert Guo (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | dbdpfy23q3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Description |
|
Reduce log volume by logging to local disk first, then logkeeper after test failed or timed out. Otherwise discard the logs.
|
| Comments |
| Comment by Aaron Morand (Inactive) [ 14/Feb/23 ] |
|
Replacing the incorrectly removed fixVersion. |
| Comment by Jeffrey Zambory [ 30/Jan/23 ] |
|
This looks to have been reverted after helping with the original logkeeper issue. Logkeeper has now been migrated to a new system - closing this as "Done". |
| Comment by Githook User [ 12/Oct/22 ] |
|
Author: {'name': 'Rob Guo', 'email': 'robert.guo@mongodb.com'}Message: |
| Comment by Max Hirschhorn [ 15/Sep/22 ] |
|
Author: {'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}Message: |