[SERVER-43591] Script to extract execution traces from mongod logs Created: 24/Sep/19  Updated: 29/Oct/23  Resolved: 15/Jan/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.3.3

Type: New Feature Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: A. Jesse Jiryu Davis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-01-13, Repl 2020-01-27
Participants:

 Description   

After a replica set test has completed, the script will find the lines in the log file that were logged specifically for TLA+ trace checking. It will merge together these lines from every replica set member's log, to produce a single execution trace for the whole system. (It will assume it can rely on timestamp order because the mongods are running on the same machine.)

Output the execution trace in a format suitable for checking it against the traces permitted by our TLA+ specs. (This format is TBD, see discussion in the TLA+ Toolbox Github project.)



 Comments   
Comment by A. Jesse Jiryu Davis [ 15/Jan/20 ]

We've decided to stop implementation and write the paper describing how far we got. See SERVER-43592 for more details on the script for extracting execution traces.

Generated at Thu Feb 08 05:03:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.