Bug #77519 Reported location of Innodb Merge Temp File is wrong
| Submitted: | 28 Jun 2015 16:01 | Modified: | 28 Aug 2018 17:26 |
|---|---|---|---|
| Reporter: | Daniël van Eeden | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
| Version: | 5.6.24, 5.6.27, 5.7.8, 5.6.40 | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[28 Jun 2015 16:01]
Daniël van Eeden
[29 Jun 2015 7:07]
MySQL Verification Team
Hello Daniël, Thank you for the report. Thanks, Umesh
[29 Jun 2015 7:08]
MySQL Verification Team
mysql> show variables like '%version%'; +-------------------------+---------------------------------------------------------+ | Variable_name | Value | +-------------------------+---------------------------------------------------------+ | innodb_version | 5.6.27 | | protocol_version | 10 | | slave_type_conversions | | | version | 5.6.27-enterprise-commercial-advanced | | version_comment | MySQL Enterprise Server - Advanced Edition (Commercial) | | version_compile_machine | x86_64 | | version_compile_os | linux-glibc2.5 | +-------------------------+---------------------------------------------------------+ 7 rows in set (0.00 sec) .. . for schema etc refer https://dev.mysql.com/doc/refman/5.6/en/innodb-create-index-examples.html#online-ddl-ex-se... mysql> create index i_dtyp_big on big_table (data_type) algorithm=inplace; Query OK, 0 rows affected (6.19 sec) Records: 0 Duplicates: 0 Warnings: 0 mysql> select * from performance_schema.events_waits_history_long where event_name='wait/io/file/innodb/innodb_temp_file' limit 1\G *************************** 1. row *************************** THREAD_ID: 20 EVENT_ID: 14208957 END_EVENT_ID: 14208957 EVENT_NAME: wait/io/file/innodb/innodb_temp_file SOURCE: row0merge.cc:3112 TIMER_START: 404909171159300 TIMER_END: 404909266345356 TIMER_WAIT: 95186056 SPINS: NULL OBJECT_SCHEMA: NULL OBJECT_NAME: /export/umesh/server/binaries/mysql-5.6.27/bug/Innodb Merge Temp File INDEX_NAME: NULL OBJECT_TYPE: FILE OBJECT_INSTANCE_BEGIN: 140347761666240 NESTING_EVENT_ID: 12459153 NESTING_EVENT_TYPE: STAGE OPERATION: close NUMBER_OF_BYTES: NULL FLAGS: NULL 1 row in set (0.00 sec) mysql> show variables like 'tmpdir'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | tmpdir | /tmp | +---------------+-------+ 1 row in set (0.00 sec) mysql>
[29 Jun 2015 8:01]
MySQL Verification Team
// 5.7.8
mysql> select * from performance_schema.events_waits_history_long where event_name='wait/io/file/innodb/innodb_temp_file' limit 1\G
*************************** 1. row ***************************
THREAD_ID: 24
EVENT_ID: 3313672
END_EVENT_ID: 3313672
EVENT_NAME: wait/io/file/innodb/innodb_temp_file
SOURCE: row0merge.cc:1049
TIMER_START: 840005960260428
TIMER_END: 840006230494396
TIMER_WAIT: 270233968
SPINS: NULL
OBJECT_SCHEMA: NULL
OBJECT_NAME: /export/umesh/server/binaries/mysql-5.7.8/bug/Innodb Merge Temp File
INDEX_NAME: NULL
OBJECT_TYPE: FILE
OBJECT_INSTANCE_BEGIN: 139872424624704
NESTING_EVENT_ID: 3210146
NESTING_EVENT_TYPE: STAGE
OPERATION: read
NUMBER_OF_BYTES: 1048576
FLAGS: NULL
1 row in set (0.00 sec)
[28 Aug 2018 17:26]
Daniel Price
Posted by developer: Fixed as of the upcoming 5.6.42, 5.7.24, 8.0.13 release, and here's the changelog entry: The location of the Innodb Merge Temp File that reported by the wait/io/file/innodb/innodb_temp_file Performance Schema instrument was incorrect.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.055 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.