Results 1 to 2 of 2
  1. #1
    Join Date
    Dec 2012
    Posts
    5

    Aborted Connections

    Hi all, I have been using MySQLTuner to assist in configuring my MySQL server.

    It is currently stating that 81% of connections are being aborted and not closing correctly, pretty much all of these will be coming from a WordPress site.

    Is there anyway of narrowing these down, and I assume it will need a modification to the WordPress code to close the connections cleanly?

    Below is the MySQLTuner output;

    Code:
    -------- General Statistics --------------------------------------------------
    [--] Skipped version check for MySQLTuner script
    [OK] Currently running supported MySQL version 5.1.66-log
    [OK] Operating on 64-bit architecture
    
    -------- Storage Engine Statistics -------------------------------------------
    [--] Status: -Archive -BDB -Federated +InnoDB -ISAM -NDBCluster
    [--] Data in MyISAM tables: 86K (Tables: 88)
    [--] Data in InnoDB tables: 1M (Tables: 20)
    [!!] Total fragmented tables: 21
    
    -------- Security Recommendations  -------------------------------------------
    [OK] All database users have passwords assigned
    
    -------- Performance Metrics -------------------------------------------------
    [--] Up for: 1h 50m 15s (22K q [3.461 qps], 2K conn, TX: 47M, RX: 2M)
    [--] Reads / Writes: 68% / 32%
    [--] Total buffers: 58.0M global + 2.7M per thread (100 max threads)
    [OK] Maximum possible memory usage: 333.0M (56% of installed RAM)
    [OK] Slow queries: 0% (17/22K)
    [OK] Highest usage of available connections: 35% (35/100)
    [OK] Key buffer size / total MyISAM indexes: 8.0M/235.0K
    [!!] Key buffer hit rate: 94.3% (227 cached / 13 reads)
    [OK] Query cache efficiency: 92.1% (18K cached / 20K selects)
    [OK] Query cache prunes per day: 0
    [OK] Sorts requiring temporary tables: 0% (0 temp sorts / 115 sorts)
    [!!] Temporary tables created on disk: 42% (54 on disk / 128 total)
    [OK] Thread cache hit rate: 79% (547 created / 2K connections)
    [OK] Table cache hit rate: 24% (96 open / 397 opened)
    [OK] Open file limit used: 14% (144/1K)
    [OK] Table locks acquired immediately: 100% (2K immediate / 2K locks)
    [!!] Connections aborted: 81%
    [OK] InnoDB data size / buffer pool: 2.0M/8.0M
    
    -------- Recommendations -----------------------------------------------------
    General recommendations:
        Run OPTIMIZE TABLE to defragment tables for better performance
        MySQL started within last 24 hours - recommendations may be inaccurate
        When making adjustments, make tmp_table_size/max_heap_table_size equal
        Reduce your SELECT DISTINCT queries without LIMIT clauses
        Your applications are not closing MySQL connections properly
    Any recommendations would be greatly appreciated!

    Thanks

  2. #2
    Join Date
    Sep 2009
    Location
    San Sebastian, Spain
    Posts
    860
    This usually suggests that the wordpress is either:

    1. is not issuing a close of the connection (in php mysql_close).
    2. The connection is sleeping longer than a specific period of time and the connection times out.
    3. The connection ended during a data transfer usually due to 2 above.

    I would look at the first possibility by simply accessing your wordpress site and then seeing if this increases.
    Ronan Cashell
    Certified Oracle DBA/Certified MySQL Expert (DBA & Cluster DBA)
    http://www.it-iss.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •