io/table/sql/handler - Amazon Aurora
Supported engine versionsContextLikely causes of increased waitsActions
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

io/table/sql/handler

The io/table/sql/handler event occurs when work has been delegated to a storage engine.

Supported engine versions

This wait event information is supported for the following engine versions:

  • Aurora MySQL version 3: 3.01.0 and 3.01.1

  • Aurora MySQL version 2

Context

The event io/table indicates a wait for access to a table. This event occurs regardless of whether the data is cached in the buffer pool or accessed on disk. The io/table/sql/handler event indicates an increase in workload activity.

A handler is a routine specialized in a certain type of data or focused on certain special tasks. For example, an event handler receives and digests events and signals from the operating system or from a user interface. A memory handler performs tasks related to memory. A file input handler is a function that receives file input and performs special tasks on the data, according to context.

Views such as performance_schema.events_waits_current often show io/table/sql/handler when the actual wait is a nested wait event such as a lock. When the actual wait isn't io/table/sql/handler, Performance Insights reports the nested wait event. When Performance Insights reports io/table/sql/handler, it represents InnoDB processing of the I/O request and not a hidden nested wait event. For more information, see Performance Schema Atom and Molecule Events in the MySQL Reference Manual.

Note

However, in Aurora MySQL versions 3.01.0 and 3.01.1, synch/mutex/innodb/aurora_lock_thread_slot_futex is reported as io/table/sql/handler.

The io/table/sql/handler event often appears in top wait events with I/O waits such as io/aurora_redo_log_flush and io/file/innodb/innodb_data_file.

Likely causes of increased waits

In Performance Insights, sudden spikes in the io/table/sql/handler event indicate an increase in workload activity. Increased activity means increased I/O.

Performance Insights filters the nesting event IDs and doesn't report a io/table/sql/handler wait when the underlying nested event is a lock wait. For example, if the root cause event is synch/mutex/innodb/aurora_lock_thread_slot_futex, Performance Insights displays this wait in top wait events and not io/table/sql/handler.

In views such as performance_schema.events_waits_current, waits for io/table/sql/handler often appear when the actual wait is a nested wait event such as a lock. When the actual wait differs from io/table/sql/handler, Performance Insights looks up the nested wait and reports the actual wait instead of io/table/sql/handler. When Performance Insights reports io/table/sql/handler, the real wait is io/table/sql/handler and not a hidden nested wait event. For more information, see Performance Schema Atom and Molecule Events in the MySQL 5.7 Reference Manual.

Note

However, in Aurora MySQL versions 3.01.0 and 3.01.1, synch/mutex/innodb/aurora_lock_thread_slot_futex is reported as io/table/sql/handler.

Actions

If this wait event dominates database activity, it doesn't necessarily indicate a performance problem. A wait event is always on top when the database is active. You need to act only when performance degrades.

We recommend different actions depending on the other wait events that you see.

Identify the sessions and queries causing the events

Typically, databases with moderate to significant load have wait events. The wait events might be acceptable if performance is optimal. If performance is isn't optimal, then examine where the database is spending the most time. Look at the wait events that contribute to the highest load, and find out whether you can optimize the database and application to reduce those events.

To find SQL queries that are responsible for high load

  1. Sign in to the Amazon Web Services Management Console and open the Amazon RDS console at https://console.amazonaws.cn/rds/.

  2. In the navigation pane, choose Performance Insights.

  3. Choose a DB instance. The Performance Insights dashboard is shown for that DB instance.

  4. In the Database load chart, choose Slice by wait.

  5. At the bottom of the page, choose Top SQL.

    The chart lists the SQL queries that are responsible for the load. Those at the top of the list are most responsible. To resolve a bottleneck, focus on these statements.

For a useful overview of troubleshooting using Performance Insights, see the blog post Analyze Amazon Aurora MySQL Workloads with Performance Insights.

Check for a correlation with Performance Insights counter metrics

Check for Performance Insights counter metrics such as Innodb_rows_changed. If counter metrics are correlated with io/table/sql/handler, follow these steps:

  1. In Performance Insights, look for the SQL statements accounting for the io/table/sql/handler top wait event. If possible, optimize this statement so that it returns fewer rows.

  2. Retrieve the top tables from the schema_table_statistics and x$schema_table_statistics views. These views show the amount of time spent per table. For more information, see The schema_table_statistics and x$schema_table_statistics Views in the MySQL Reference Manual.

    By default, rows are sorted by descending total wait time. Tables with the most contention appear first. The output indicates whether time is spent on reads, writes, fetches, inserts, updates, or deletes. The following example was run on an Aurora MySQL 2.09.1 instance.

    mysql> select * from sys.schema_table_statistics limit 1\G

*************************** 1. row ***************************
     table_schema: read_only_db
       table_name: sbtest41
    total_latency: 54.11 m
     rows_fetched: 6001557
    fetch_latency: 39.14 m
    rows_inserted: 14833
   insert_latency: 5.78 m
     rows_updated: 30470
   update_latency: 5.39 m
     rows_deleted: 14833
   delete_latency: 3.81 m
 io_read_requests: NULL
          io_read: NULL
  io_read_latency: NULL
io_write_requests: NULL
         io_write: NULL
 io_write_latency: NULL
 io_misc_requests: NULL
  io_misc_latency: NULL
1 row in set (0.11 sec)

Check for other correlated wait events

If synch/sxlock/innodb/btr_search_latch and io/table/sql/handler contribute most to the DB load anomaly together, check whether the innodb_adaptive_hash_index variable is turned on. If it is, consider increasing the innodb_adaptive_hash_index_parts parameter value.

If the Adaptive Hash Index is turned off, consider turning it on. To learn more about the MySQL Adaptive Hash Index, see the following resources:

Note

The Adaptive Hash Index isn't supported on Aurora reader DB instances.

In some cases, performance might be poor on a reader instance when synch/sxlock/innodb/btr_search_latch and io/table/sql/handler are dominant. If so, consider redirecting the workload temporarily to the writer DB instance and turning on the Adaptive Hash Index.