pt-query-digest reports Binlog Dump as slow query

Bug #1556086 reported by Francisco Bordenave
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Triaged
Medium
Frank Cizmich

Bug Description

pt-query-digest reports administrative command Binlog Dump as slow query, as follows:
# Profile
# Rank Query ID Response time Calls R/Call V/M Item
# ==== ================== ================== ====== =========== ===== ====
# 1 0xCBC895EB5A636382 2034253.9169 89.9% 3 678084.6390 45... ADMIN BINLOG DUMP

# Query 1: 0.00 QPS, 6.39x concurrency, ID 0xCBC895EB5A636382 at byte 898329113
# This item is included in the report because it matches --limit.
# Scores: V/M = 454071.00
# Time range: 2016-03-04 11:38:49 to 2016-03-08 04:02:32
# Attribute pct total min max avg 95% stddev median
# ============ === ======= ======= ======= ======= ======= ======= =======
# Count 0 3
# Exec time 89 2034254s 260768s 1467073s 678085s 1454312s 554886s 305211s
# Lock time 0 0 0 0 0 0 0 0
# Rows sent 0 0 0 0 0 0 0 0
# Rows examine 0 0 0 0 0 0 0 0
# Rows affecte 0 0 0 0 0 0 0 0
# Bytes sent 1 7.20G 1.84G 3.53G 2.40G 3.49G 834.59M 1.76G
# Merge passes 0 0 0 0 0 0 0 0
# Tmp tables 0 0 0 0 0 0 0 0
# Tmp disk tbl 0 0 0 0 0 0 0 0
# Tmp tbl size 0 0 0 0 0 0 0 0
# Query size 0 102 34 34 34 34 0 34
# String:
# Databases pa_1430_pr... (1/33%), pa_1560_pr... (1/33%)... 1 more
# Hosts 192.168.100.129 (2/66%), 192.168.100.82 (1/33%)
# Users percona (2/66%), repl (1/33%)
# Query_time distribution
# 1us
# 10us
# 100us
# 1ms
# 10ms
# 100ms
# 1s
# 10s+ ################################################################
administrator command: Binlog Dump\G

In my opinion it should skip this statement by default since we expect to see it as longest running query.

Revision history for this message
Kenny Gryp (gryp) wrote :

Yes, I agree.

At least we should document this clearly in the pt-query-digest manual and mention how to filter them out.

Or filter it out by default and document how to disable it (maybe there's a use case where we want it anyway)

Changed in percona-toolkit:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Frank Cizmich (frank-cizmich)
milestone: none → 2.2.18
status: Triaged → In Progress
Changed in percona-toolkit:
milestone: 2.2.18 → 2.2.19
Changed in percona-toolkit:
milestone: 2.2.19 → 2.2.20
Changed in percona-toolkit:
status: In Progress → Confirmed
status: Confirmed → Triaged
milestone: 2.2.20 → 2.2.21
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-703

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.