max_statement_time is not honored when query is doing InnoDB_queue_wait

[Ovais Tariq]

It seems like that max_statement_time is not being honored when the query is waiting in InnoDB wait queue. An example can be seen below:

# User@Host: REDACTED[REDACTED] @ [10.164.7.49] Id: 70738266
# Schema: Last_errno: 1030 Killed: 0
# Query_time: 1.211006 Lock_time: 0.000240 Rows_sent: 0 Rows_examined: 0 Rows_affected: 0
# Bytes_sent: 701 Tmp_tables: 0 Tmp_disk_tables: 0 Tmp_table_sizes: 0
# InnoDB_trx_id: 5F591B4EB
# QC_Hit: No Full_scan: No Full_join: No Tmp_table: No Tmp_table_on_disk: No
# Filesort: No Filesort_on_disk: No Merge_passes: 0
# InnoDB_IO_r_ops: 0 InnoDB_IO_r_bytes: 0 InnoDB_IO_r_wait: 0.000000
# InnoDB_rec_lock_wait: 0.000000 InnoDB_queue_wait: 1.206270
# InnoDB_pages_distinct: 9
# Log_slow_rate_type: query Log_slow_rate_limit: 100
SET timestamp=1495557472;
SET STATEMENT max_statement_time=189 FOR SELECT `col1`, `col2`, `col3`, `col4`, `col5` FROM db.tbl_name WHERE (`col2`='xxx') AND (`col3`='yyy');

Percona Server version: 5.6.35-80.0

[Fernando Ipar (fipar)]

I think it is not honored for any blocking condition. See my comment with the test while trying to do load data infile from a broken fifo on this report, for example: https://bugs.mysql.com/bug.php?id=75161

[Shahriyar Rzayev (rzayev-sehriyar)]

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