Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Issues

Select view

Select search mode

 
12 of 12

pt-query-digest no longer understands binlog format

Incomplete

Description

pt-query-digest no longer seems to be able to process binlogs, possibly due to minor changes in mysqlbinlog output on MariaDB 10.6.x

mysqlbinlog mysql-bin.000001 > mysql-bin.000001.txt pt-query-digest --type binlog mysql-bin.000001.txt

This erroneously produces output that seems to be garbage:

# Overall: 0 total, 469.93k unique, 0 QPS, 0x concurrency ________________ # Time range: all events occurred at 2024-01-19 13:54:47 # Attribute total min max avg 95% stddev median # ============ ======= ======= ======= ======= ======= ======= ======= # Query size 1.97G 119 116.81k 4.14k 4.27k 1.00k 4.27k # Profile # Rank Query ID Response time Calls R/Call V # ====== =================================== ====== ====== ====== ===== ==

Environment

MariaDB 10.6, CentOS 7

Details

Assignee

Reporter

Priority

Components

Affects versions

Needs QA

Yes

Smart Checklist

Created January 20, 2024 at 10:30 AM
Updated September 7, 2024 at 1:40 PM
Resolved September 7, 2024 at 1:40 PM

Activity

Aaditya DubeySeptember 7, 2024 at 1:39 PM

Hi

We still haven't heard any news from you. So, I assume the issue no longer persists and will close the ticket. If you disagree, reply and create a follow-up with a new Jira report.

Aaditya DubeyJanuary 27, 2024 at 5:00 PM

Hi

Thank you for the report.
I don't see garbage output which is mentioned in the report, Please check my test case below:

MariaDB : 10.6.15 ./mariadb-binlog $HOME/sandboxes/msb_mdb10_6_15/data/1.000001 > mysql-bin.000001.txt $:~/percona-toolkit-3.5.7/bin$ ./pt-query-digest --type binlog $HOME/mdb10.6.15/bin/mysql-bin.000001.txt # 11.9s user time, 170ms system time, 39.97M rss, 48.09M vsz # Current date: Sat Jan 27 09:20:27 2024 # Hostname: localhost # Files: $HOME/mdb10.6.15/bin/mysql-bin.000001.txt # Overall: 88.22k total, 10 unique, 653.47 QPS, 0.13x concurrency ________ # Time range: 2024-01-27 09:13:02 to 09:15:17 # Attribute total min max avg 95% stddev median # ============ ======= ======= ======= ======= ======= ======= ======= # Exec time 18s 0 1s 204us 0 14ms 0 # Query size 10.77M 1 187.43k 102.39 234.30 1.23k 36.69 # @@session.au 1 1 1 1 1 0 1 # @@session.au 1 1 1 1 1 0 1 # @@session.au 1 1 1 1 1 0 1 # @@session.ch 1 1 1 1 1 0 1 # @@session.co 192 192 192 192 192 0 192 # @@session.co 192 192 192 192 192 0 192 # @@session.ex 0 0 0 0 0 0 0 # @@session.fo 1 1 1 1 1 0 1 # @@session.lc 0 0 0 0 0 0 0 # @@session.ps 46 46 46 46 46 0 46 # @@session.sq 0 0 0 0 0 0 0 # @@session.sq 0 0 0 0 0 0 0 # @@session.sq 1.31G 1.31G 1.31G 1.31G 1.31G 0 1.31G # @@session.un 1 1 1 1 1 0 1 # error code 0 0 0 0 0 0 0 # Profile # Rank Query ID Response time Calls R/Call V/M # ==== =================================== ============= ===== ====== ==== # 1 0x410C2605CF6B250BE96B374065B13356 7.0000 38.9% 22052 0.0003 0.98 UPDATE sbtest? # 2 0xB2249CB854EE3C2AD30AD7E3079ABCE7 6.0000 33.3% 22052 0.0003 0.98 UPDATE sbtest? # 3 0xDDBF88031795EC65EAB8A8A8BEEFF705 3.0000 16.7% 22052 0.0001 0.98 DELETE sbtest? # 4 0x6C545CFB55365122F1256A27240AEFC7 2.0000 11.1% 22052 0.0001 0.98 INSERT sbtest? # MISC 0xMISC ... # SHOW TABLE STATUS FROM `testdb` LIKE 'sbtest2'\G # SHOW CREATE TABLE `testdb`.`sbtest2`\G INSERT INTO sbtest2 (id, k, c, pad) VALUES (589, 559, '68510587569-32472392566-32762955166-05232734883-68725489392-34946682330-99331942797-01238712037-60107796176-93769343606', '09088476629-68132328485-42376027368-50713192423-80725218111')\G

Please share complete test case where you seeing the issue.