Issue on my side with replay about workloadtools HOT 3 CLOSED

I'm not really sure that you can avoid this type of errors completely. There will always be a number of events that you will not be able to replay, especially at the beginning of the replay itself.
The ideal solution depends on what you are trying to achieve: are you trying to compare production with test, test with test? What is the purpose of the replay?
Depending on the answer, you could:

1. Ignore the errors. If you are comparing a first replay on test with a second replay on test, both replays will get the same errors, so the comparison is still fair
2. Remove the offending events from the captured events. If you need the replay to contain 0 errors, you could open the source .sqlite file with a sqlite client like DB Browser for Sqlite and delete the events that are causing trouble. You could even decide to delete the first 5 or more minutes of events. If this solution suits you, I could add a property to make the replay skip a certain amount of minutes or events before enqueueing events for replay.

Hope this helps

from workloadtools.

Hello,

After a while we have conclusion. We used MARK (Begin Transaction With Mark) to get highlight spot. Using this we restored Backup and Logs to the MARK point and started replay from the beginning (when the Capture started). Quick little question at the end. These little files after the Capture was concluded, are they containing data from the main TEMP file and are therefore to inject some small samples or just doing the check of the capture file (sqlite)?

Capture is creating big TEMP file, these cache files are there after the capture was concluded.

Edit: I know there is a CACHE option in JSON (We have not defined it). But I am not entirely sure of the purpose of these files (around 100 before we shutted all down for good, 'cause the CMD were not writing a thing anymore and only these CACHE files were popping up, we used the timer option in JSON).

from workloadtools.

Glad you sorted it out!
Regarding the cache files, those are for caching events to disk before processing them. The events queue is a memory-mapped file and needs the cache to avoid using all the memory in the host. I'm surprised those file don't get deleted though, this is not the intended behavior. Thanks for reporting it, I'll have a look at the code.

from workloadtools.