[SERVER-50856] Dump All Logs After Recording a Failure Created: 10/Sep/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Tooling & Methods
|
| Participants: |
| Description |
|
It would be useful for distributed use cases to dump all sharding or repl logs when a test fails and a recording is generated. The dumped logs should follow a similar format to the real-time logs, where logs from all processes in the relevant processes are logged in chronological order. There also needs to be clear indication that they are retroactively applied. This ticket will add retro logging for all logs with the replication component and will be set in a new resmoke logging configuration file (in resmokeconfig/loggers). the "replica_sets". suite will be updated to use the new logging configuration and work to add logging to remaining DS suites will be ticketed out after this ticket is code complete. |
| Comments |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |