Currently percona-playback relies on thread_id to be present in the log to be able to differentiate between different sessions

Bug #1186371 reported by Ovais Tariq
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MOVED - Percona Playback
New
Undecided
Unassigned

Bug Description

Currently percona-playback relies on Thread_id to be present in the log to be able to differentiate between the sessions. Upstream MySQL doesn't log the thread_id and hence percona-playback cannot be used to replay a realistic workload using upstream's slow log, because in that case all the queries are replayed using a single thread.

Revision history for this message
Marek G (m-gizynski) wrote :

You can use

sed 's/] Id:/] Thread_id:/'

as workaround.

Revision history for this message
Ovais Tariq (ovais-tariq) wrote :

This workaround will not work with every MySQL version. See a snippet of slow query log from MySQL 5.1 below:

# Time: 141009 16:51:35
# User@Host: msandbox[msandbox] @ localhost []
# Query_time: 0.015884 Lock_time: 0.000045 Rows_sent: 10 Rows_examined: 10
SET timestamp=1412866295;
select * from perm_conf limit 10;

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.