GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

ADMIN QUIT - showing up in slow query log

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • ADMIN QUIT - showing up in slow query log

    Hi,

    I'm not sure what this means, running mk-query-digest on our slow query log and seeing this line as the first item:

    # 1 0xAA353644DE4C4CB4 2116.5141 28.6% 2025 1.0452 ADMIN QUIT

    What does it mean and why is it happening so many times and why is it taking more than .5 seconds?

    Is this an issue, i.e. do we care?


    # Query 1: 0.17 QPS, 0.18x concurrency, ID 0xAA353644DE4C4CB4 at byte 2679343
    # This item is included in the report because it matches --limit.
    # pct total min max avg 95% stddev median
    # Count 23 2025
    # Exec time 22 2117s 500ms 3s 1s 2s 433ms 857ms
    # Lock time 0 0 0 0 0 0 0 0
    # Rows sent 0 0 0 0 0 0 0 0
    # Rows exam 0 0 0 0 0 0 0 0
    # Users 1 dbuser
    # Hosts 1
    # Databases 1 ourdb
    # Time range 2010-09-29 09:07:35 to 2010-09-29 12:25:23
    # bytes 5 53.39k 27 27 27 27 0 27
    # Rows affe 0 908 0 1 0.45 0.99 0.49 0
    # Rows read 0 0 0 0 0 0 0 0
    # Query_time distribution
    # 1us
    # 10us
    # 100us
    # 1ms
    # 10ms
    # 100ms ################################################## ########## ####
    # 1s ################################################
    # 10s+
    administrator command: Quit\G

  • #2
    It has been a while since I've had my head deeply in the protocol parsing code, but I think this is spurious noise, and can be ignored. It's caused by things such as out-of-order packets, failure to parse packets correctly, etc.

    Comment

    Working...
    X