What you wanted to know about MySQL, but could not find using inernal instrumentation only
-
Upload
sveta-smirnova -
Category
Software
-
view
184 -
download
1
Transcript of What you wanted to know about MySQL, but could not find using inernal instrumentation only
![Page 1: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/1.jpg)
What you wanted to know about MySQLbut could not find using internal instrumentation only
February, 3, 2017
Sveta Smirnova
![Page 2: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/2.jpg)
∙ MySQL Support engineer∙ Author of
∙ MySQL Troubleshooting∙ JSON UDF functions∙ FILTER clause for MySQL
∙ Speaker∙ Percona Live, OOW, Fosdem,
DevConf, HighLoad...
Sveta Smirnova
2
![Page 3: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/3.jpg)
Year 2009
3
![Page 4: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/4.jpg)
∙ In modern versions we have a lot of onlineinformation
∙ However users usually notice error from logfiles, when context is already gone
∙ Partially this is solved by modern monitoringtools (PMM) which can save historicalstatistics
∙ But not about everything
Historical Data
4
![Page 5: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/5.jpg)
∙ In modern versions we have a lot of onlineinformation
∙ However users usually notice error from logfiles, when context is already gone
∙ Partially this is solved by modern monitoringtools (PMM) which can save historicalstatistics
∙ But not about everything
Historical Data
4
![Page 6: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/6.jpg)
∙ In modern versions we have a lot of onlineinformation
∙ However users usually notice error from logfiles, when context is already gone
∙ Partially this is solved by modern monitoringtools (PMM) which can save historicalstatistics
∙ But not about everything
Historical Data
4
![Page 7: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/7.jpg)
∙ In modern versions we have a lot of onlineinformation
∙ However users usually notice error from logfiles, when context is already gone
∙ Partially this is solved by modern monitoringtools (PMM) which can save historicalstatistics
∙ But not about everything
Historical Data
4
![Page 8: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/8.jpg)
∙ It is easy to find in the Audit log records querywhich failed with this error<AUDIT_RECORD
NAME="Query"RECORD="2_2017-01-12T20:40:36"
TIMESTAMP="2017-01-12T20:41:32 UTC"COMMAND_CLASS="update"CONNECTION_ID="3"
STATUS=" 1205"SQLTEXT="update t1 set f1=f1-1"
USER="root[root] @ localhost [127.0.0.1]"HOST="localhost"
OS_USER=IP="127.0.0.1"DB="test"
/>
∙ But there is the query which holds the lock?∙ Even hard to find online∙ Multiple statement transactions make it worse∙ However server has all information to print all
queries of locking transaction∙ MySQL Bug #84563
Lock wait timeout
5
![Page 9: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/9.jpg)
∙ It is easy to find in the Audit log records querywhich failed with this error
∙ But there is the query which holds the lock?
∙ Even hard to find online∙ Multiple statement transactions make it worse∙ However server has all information to print all
queries of locking transaction∙ MySQL Bug #84563
Lock wait timeout
5
![Page 10: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/10.jpg)
∙ It is easy to find in the Audit log records querywhich failed with this error
∙ But there is the query which holds the lock?∙ Even hard to find online∙ Especially if you have thousands of running
threads!
∙ Multiple statement transactions make it worse∙ However server has all information to print all
queries of locking transaction∙ MySQL Bug #84563
Lock wait timeout
5
![Page 11: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/11.jpg)
∙ It is easy to find in the Audit log records querywhich failed with this error
∙ But there is the query which holds the lock?∙ Even hard to find online∙ Multiple statement transactions make it worse
∙ However server has all information to print allqueries of locking transaction
∙ MySQL Bug #84563
Lock wait timeout
5
![Page 12: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/12.jpg)
∙ It is easy to find in the Audit log records querywhich failed with this error
∙ But there is the query which holds the lock?∙ Even hard to find online∙ Multiple statement transactions make it worse∙ However server has all information to print all
queries of locking transaction
∙ MySQL Bug #84563
Lock wait timeout
5
![Page 13: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/13.jpg)
∙ It is easy to find in the Audit log records querywhich failed with this error
∙ But there is the query which holds the lock?∙ Even hard to find online∙ Multiple statement transactions make it worse∙ However server has all information to print all
queries of locking transaction∙ MySQL Bug #84563
Lock wait timeout
5
![Page 14: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/14.jpg)
∙ First transaction––––––––––––LATEST DETECTED DEADLOCK––––––––––––2017-01-19 13:03:42 7f37fc636700*** (1) TRANSACTION:TRANSACTION 1298, ACTIVE 3 sec starting index read...DELETE FROM t WHERE i = 1*** (1) WAITING FOR THIS LOCK TO BE GRANTED:RECORD LOCKS space id 0 page no 314 n bits 72 index ‘GEN_CLUST_INDEX‘of table ‘test‘.‘t‘ trx id 1298 lock_mode X waiting...
∙ Second transaction∙ Which query held the lock?∙ SELECT * FROM t WHERE i = 1 LOCK IN SHARE MODE;
∙ How would we know?∙ refman/.../innodb-deadlock-example.html∙ Bug #84607
What exactly caused the deadlock?
6
![Page 15: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/15.jpg)
∙ First transaction∙ Second transaction
*** (2) TRANSACTION:TRANSACTION 1297, ACTIVE 7 sec starting index read...DELETE FROM t WHERE i = 1*** (2) HOLDS THE LOCK(S):RECORD LOCKS space id 0 page no 314 n bits 72 index ‘GEN_CLUST_INDEX‘...*** (2) WAITING FOR THIS LOCK TO BE GRANTED:RECORD LOCKS space id 0 page no 314 n bits 72 index ‘GEN_CLUST_INDEX‘...*** WE ROLL BACK TRANSACTION (1)
∙ Which query held the lock?∙ SELECT * FROM t WHERE i = 1 LOCK IN SHARE MODE;
∙ How would we know?∙ refman/.../innodb-deadlock-example.html∙ Bug #84607
What exactly caused the deadlock?
6
![Page 16: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/16.jpg)
∙ First transaction∙ Second transaction∙ Which query held the lock?
∙ SELECT * FROM t WHERE i = 1 LOCK IN SHARE MODE;
∙ How would we know?∙ refman/.../innodb-deadlock-example.html∙ Bug #84607
What exactly caused the deadlock?
6
![Page 17: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/17.jpg)
∙ First transaction∙ Second transaction∙ Which query held the lock?∙ SELECT * FROM t WHERE i = 1 LOCK IN SHARE MODE;
∙ How would we know?∙ refman/.../innodb-deadlock-example.html∙ Bug #84607
What exactly caused the deadlock?
6
![Page 18: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/18.jpg)
∙ First transaction∙ Second transaction∙ Which query held the lock?∙ SELECT * FROM t WHERE i = 1 LOCK IN SHARE MODE;
∙ How would we know?
∙ refman/.../innodb-deadlock-example.html∙ Bug #84607
What exactly caused the deadlock?
6
![Page 19: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/19.jpg)
∙ First transaction∙ Second transaction∙ Which query held the lock?∙ SELECT * FROM t WHERE i = 1 LOCK IN SHARE MODE;
∙ How would we know?∙ refman/.../innodb-deadlock-example.html
∙ Bug #84607
What exactly caused the deadlock?
6
![Page 20: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/20.jpg)
∙ First transaction∙ Second transaction∙ Which query held the lock?∙ SELECT * FROM t WHERE i = 1 LOCK IN SHARE MODE;
∙ How would we know?∙ refman/.../innodb-deadlock-example.html∙ Bug #84607
What exactly caused the deadlock?
6
![Page 21: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/21.jpg)
∙ Performance Schema∙ Bug #71364 Please provide warning text
information into P_S∙ Bug #61030 Make an I_S table of client error
codes∙ Bug #58058 please add instrumentation to track
error counts on a server
∙ General logging
Some past requests
7
![Page 22: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/22.jpg)
∙ Performance Schema∙ General logging
∙ Bug #70796 Error messages and warnings forsql-mode behaviours need more verbosity
∙ Bug #64190 Log failed queries in a separate log∙ Bug #60884 Enable logging of all errors to the
error log∙ Bug #34137 Additional logging of the server
shutdown process
Some past requests
7
![Page 23: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/23.jpg)
∙ Which kind of query can produce this output?∙ t is InnoDB table
mysql> select * from table_handles where object_name=’t’\G*************************** 1. row ***************************
OBJECT_TYPE: TABLEOBJECT_SCHEMA: test
OBJECT_NAME: tOBJECT_INSTANCE_BEGIN: 140108477034256
OWNER_THREAD_ID: 23OWNER_EVENT_ID: 3788INTERNAL_LOCK: NULLEXTERNAL_LOCK: READ EXTERNAL
1 row in set (0,00 sec)
∙ Bug #84609∙ Bug #84610
Table_handles
8
![Page 24: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/24.jpg)
∙ Which kind of query can produce this output?∙ lock table t read;
∙ Bug #84609∙ Bug #84610
Table_handles
8
![Page 25: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/25.jpg)
∙ Which kind of query can produce this output?∙ lock table t read;∙ select * from t [lock in share mode];
∙ Bug #84609∙ Bug #84610
Table_handles
8
![Page 26: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/26.jpg)
∙ Which kind of query can produce this output?∙ lock table t read;∙ select * from t [lock in share mode];∙ select * from t where i [=,in,<,>] ...
∙ Bug #84609∙ Bug #84610
Table_handles
8
![Page 27: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/27.jpg)
∙ Which kind of query can produce this output?∙ lock table t read;∙ select * from t [lock in share mode];∙ select * from t where i [=,in,<,>] ...∙ But not select * from t where unique_key = ... !
∙ Bug #84609∙ Bug #84610
Table_handles
8
![Page 28: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/28.jpg)
∙ Which kind of query can produce this output?∙ t is InnoDB table
mysql> select * from table_handles where object_name=’t’\G*************************** 1. row ***************************
OBJECT_TYPE: TABLEOBJECT_SCHEMA: test
OBJECT_NAME: tOBJECT_INSTANCE_BEGIN: 140108477034256
OWNER_THREAD_ID: 23OWNER_EVENT_ID: 4379INTERNAL_LOCK: NULLEXTERNAL_LOCK: WRITE EXTERNAL
1 row in set (0,00 sec)
∙ Bug #84609∙ Bug #84610
Table_handles
8
![Page 29: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/29.jpg)
∙ Which kind of query can produce this output?∙ lock table t write;
∙ Manual says: "The table lock used at the storageengine level. The value is one of READEXTERNAL or WRITE EXTERNAL."
∙ Is this storage engine level operation?
∙ Bug #84609∙ Bug #84610
Table_handles
8
![Page 30: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/30.jpg)
∙ Which kind of query can produce this output?∙ lock table t write;∙ select * from t for update;
∙ Bug #84609∙ Bug #84610
Table_handles
8
![Page 31: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/31.jpg)
∙ Which kind of query can produce this output?∙ lock table t write;∙ select * from t for update;∙ update t set i=i+sleep(i) where i [=,in,<,>] ...
∙ Bug #84609∙ Bug #84610
Table_handles
8
![Page 32: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/32.jpg)
∙ Which kind of query can produce this output?∙ Bug #84609
∙ Bug #84610
Table_handles
8
![Page 33: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/33.jpg)
∙ Which kind of query can produce this output?∙ Bug #84609∙ Bug #84610
Table_handles
8
![Page 34: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/34.jpg)
∙ In past we had only one troubleshooting tool∙ SHOW SLAVE STATUS
∙ Today Performance Schema supportsreplication
∙ But it still misses
Replication
9
![Page 35: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/35.jpg)
∙ In past we had only one troubleshooting tool∙ Today Performance Schema supports
replication
∙ But it still misses
Replication
9
![Page 36: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/36.jpg)
∙ In past we had only one troubleshooting tool∙ Today Performance Schema supports
replication∙ But it still misses
∙ Bug #81249 SLAVE_NET_TIMEOUT TOP_S FOR SLAVE THREAD VARIABLES
∙ Bug #78918 Metric for succesful slave reconnects∙ Bug #77605 Add more information to SQL
thread-related P_S tables
Replication
9
![Page 37: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/37.jpg)
∙ In past we had only one troubleshooting tool∙ Today Performance Schema supports
replication∙ But it still misses
∙ Bug #76828 Slave details on a master∙ Bug #74809 Stats per binlog event type∙ Bug #72826 Support for joining
replication_execute_status_by_%∙ Bug #70951 Threads shutdown info
Replication
9
![Page 38: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/38.jpg)
∙ What does this output mean?2017-01-20T21:44:52.301177Z 5 [Note] Aborted connection 5 to db: ’test’ user: ’root’host: ’localhost’ (Got timeout reading communication packets)
∙ Timeout while connection was establishing?∙ Connection was aborted, because
interactive_timeout/wait_timeout passed?∙ Something else?∙ Bug #51219, Bug #28836, Bug #78843, Bug
#84612
Connection errors
10
![Page 39: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/39.jpg)
∙ What does this output mean?∙ Timeout while connection was establishing?
∙ Connection was aborted, becauseinteractive_timeout/wait_timeout passed?
∙ Something else?∙ Bug #51219, Bug #28836, Bug #78843, Bug
#84612
Connection errors
10
![Page 40: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/40.jpg)
∙ What does this output mean?∙ Timeout while connection was establishing?∙ Connection was aborted, because
interactive_timeout/wait_timeout passed?
∙ Something else?∙ Bug #51219, Bug #28836, Bug #78843, Bug
#84612
Connection errors
10
![Page 41: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/41.jpg)
∙ What does this output mean?∙ Timeout while connection was establishing?∙ Connection was aborted, because
interactive_timeout/wait_timeout passed?∙ Something else?
∙ Bug #51219, Bug #28836, Bug #78843, Bug#84612
Connection errors
10
![Page 42: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/42.jpg)
∙ What does this output mean?∙ Timeout while connection was establishing?∙ Connection was aborted, because
interactive_timeout/wait_timeout passed?∙ Something else?∙ Bug #51219, Bug #28836, Bug #78843, Bug
#84612
Connection errors
10
![Page 43: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/43.jpg)
∙ Bug #77888 max_used_connection peruser/account missing in P_S/sys
∙ Bug #77581 Collect DNS timing informationinto Performance_Schema
∙ Bug #76403COUNT_ABORTED_CLIENT_ERRORS toP_S.host_cache
∙ Bug #72219 First and last connectiontimestamps to P_S.users table
Other connection requests
11
![Page 44: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/44.jpg)
∙ Bug #71305PERFORMANCE_SCHEMA.THREADStable, add a PORT column
∙ Bug #71186 P_S.host_cache does not collectconnections aborted entries
∙ Bug #69880 Track and expose connectioncreation timestamp
Other connection requests
11
![Page 45: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/45.jpg)
∙ Bug #69725 P_S.socket_instances doesn’tinclude named pipe or shared memoryconnections
∙ Bug #45817 Please add SHOW command forinc_host_errors(max_connect_errors)
∙ Bug #21565 More verbose connection log
Other connection requests
11
![Page 46: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/46.jpg)
∙ One more outputmysql> flush status;Query OK, 0 rows affected (0,00 sec)
mysql> select ...600048 rows in set (1 min 17,26 sec)
mysql> show status like ’Created_tmp%’;+-------------------------+-------+| Variable_name | Value |+-------------------------+-------+| Created_tmp_disk_tables | 2 || Created_tmp_files | 6 || Created_tmp_tables | 3 |+-------------------------+-------+3 rows in set (0,00 sec)
∙ Were tables created in simultaneously?∙ What is their size?∙ Solution: watch lsof∙ Bug #74484∙ Bug #84613
Temporary tables
12
![Page 47: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/47.jpg)
∙ One more output∙ Were tables created in simultaneously?
∙ What is their size?∙ Solution: watch lsof∙ Bug #74484∙ Bug #84613
Temporary tables
12
![Page 48: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/48.jpg)
∙ One more output∙ Were tables created in simultaneously?∙ What is their size?
∙ Solution: watch lsof∙ Bug #74484∙ Bug #84613
Temporary tables
12
![Page 49: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/49.jpg)
∙ One more output∙ Were tables created in simultaneously?∙ What is their size?∙ Solution: watch lsof
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAMEmysqld 8697 sveta 70u REG 0,43 11765657 43001204 /tmp/mysqld.1/MYSeEOHe (deleted)mysqld 8697 sveta 71u REG 0,43 11765657 43001205 /tmp/mysqld.1/MYVwF8Od (deleted)
∙ Bug #74484∙ Bug #84613
Temporary tables
12
![Page 50: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/50.jpg)
∙ One more output∙ Were tables created in simultaneously?∙ What is their size?∙ Solution: watch lsof∙ Bug #74484
∙ Bug #84613
Temporary tables
12
![Page 51: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/51.jpg)
∙ One more output∙ Were tables created in simultaneously?∙ What is their size?∙ Solution: watch lsof∙ Bug #74484∙ Bug #84613
Temporary tables
12
![Page 52: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/52.jpg)
∙ I_S.OPTIMIZER_TRACE is good addition forOptimizer
∙ But what about other parts of the server?
∙ Runtime∙ Parser∙ Binary logging∙ InnoDB
∙ Bug #84620
Trace
13
![Page 53: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/53.jpg)
∙ I_S.OPTIMIZER_TRACE is good addition forOptimizer
∙ But what about other parts of the server?
∙ Runtime∙ Parser∙ Binary logging∙ InnoDB
∙ Bug #84620
Trace
13
![Page 54: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/54.jpg)
∙ I_S.OPTIMIZER_TRACE is good addition forOptimizer
∙ But what about other parts of the server?∙ Runtime
∙ Parser∙ Binary logging∙ InnoDB
∙ Bug #84620
Trace
13
![Page 55: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/55.jpg)
∙ I_S.OPTIMIZER_TRACE is good addition forOptimizer
∙ But what about other parts of the server?∙ Runtime∙ Parser
∙ Binary logging∙ InnoDB
∙ Bug #84620
Trace
13
![Page 56: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/56.jpg)
∙ I_S.OPTIMIZER_TRACE is good addition forOptimizer
∙ But what about other parts of the server?∙ Runtime∙ Parser∙ Binary logging
∙ InnoDB∙ Bug #84620
Trace
13
![Page 57: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/57.jpg)
∙ I_S.OPTIMIZER_TRACE is good addition forOptimizer
∙ But what about other parts of the server?∙ Runtime∙ Parser∙ Binary logging∙ InnoDB
∙ Bug #84620
Trace
13
![Page 58: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/58.jpg)
∙ I_S.OPTIMIZER_TRACE is good addition forOptimizer
∙ But what about other parts of the server?∙ Runtime∙ Parser∙ Binary logging∙ InnoDB
∙ Bug #84620
Trace
13
![Page 59: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/59.jpg)
∙ General∙ Bug #83626 Collect per column usage data in
performance_schema∙ Bug #71755 Provide per partition summary
information in PERFORMANCE_SCHEMA∙ Bug #81020 performance_schema: Please add
optimizer usage statistics∙ Bug #55171 How much sort_buffer_size are
actually used?
∙ InnoDB
More tracing requests
14
![Page 60: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/60.jpg)
∙ General∙ InnoDB
∙ Bug #81611 Add P_S metrics to collectcompressed page bytes vs other types written torelog
∙ Bug #78448 Provide better metrics oninnodb_sort_buffer_size usage
∙ Bug #71698 Add instrumentation for thedoublewrite buffer and undo segments
More tracing requests
14
![Page 61: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/61.jpg)
∙ SHOW PROCESSLIST has multiple states
∙ Some of them are clear∙ But what do these mean?∙ Bug #57544∙ Bug#72083∙ Bug #84615
Vague stages
15
![Page 62: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/62.jpg)
∙ SHOW PROCESSLIST has multiple states∙ Some of them are clear
∙ But what do these mean?∙ Bug #57544∙ Bug#72083∙ Bug #84615
Vague stages
15
![Page 63: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/63.jpg)
∙ SHOW PROCESSLIST has multiple states∙ Some of them are clear∙ But what do these mean?
∙ System lock∙ statistics∙ freeing items∙ Sending data∙ cleaning up∙ closing tables∙ end
∙ Bug #57544∙ Bug#72083∙ Bug #84615
Vague stages
15
![Page 64: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/64.jpg)
∙ SHOW PROCESSLIST has multiple states∙ Some of them are clear∙ But what do these mean?∙ Bug #57544
∙ Bug#72083∙ Bug #84615
Vague stages
15
![Page 65: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/65.jpg)
∙ SHOW PROCESSLIST has multiple states∙ Some of them are clear∙ But what do these mean?∙ Bug #57544∙ Bug#72083
∙ Bug #84615
Vague stages
15
![Page 66: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/66.jpg)
∙ SHOW PROCESSLIST has multiple states∙ Some of them are clear∙ But what do these mean?∙ Bug #57544∙ Bug#72083∙ Bug #84615
Vague stages
15
![Page 67: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/67.jpg)
Summary
![Page 68: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/68.jpg)
∙ Feature requests∙ Comments∙ Fixes
To better MySQL!
17
![Page 69: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/69.jpg)
http://www.slideshare.net/SvetaSmirnova
https://twitter.com/svetsmirnova
https://github.com/svetasmirnova
Thank you!
18
![Page 70: What you wanted to know about MySQL, but could not find using inernal instrumentation only](https://reader031.fdocuments.in/reader031/viewer/2022030113/589a41621a28ab8c588b6403/html5/thumbnails/70.jpg)
DATABASE PERFORMANCEMATTERS