mirror of
https://github.com/MariaDB/server.git
synced 2025-08-26 01:44:06 +03:00
378cdc58c1
bug #57006 "Deadlock between HANDLER and FLUSH TABLES WITH READ LOCK" and bug #54673 "It takes too long to get readlock for 'FLUSH TABLES WITH READ LOCK'". The first bug manifested itself as a deadlock which occurred when a connection, which had some table open through HANDLER statement, tried to update some data through DML statement while another connection tried to execute FLUSH TABLES WITH READ LOCK concurrently. What happened was that FTWRL in the second connection managed to perform first step of GRL acquisition and thus blocked all upcoming DML. After that it started to wait for table open through HANDLER statement to be flushed. When the first connection tried to execute DML it has started to wait for GRL/the second connection creating deadlock. The second bug manifested itself as starvation of FLUSH TABLES WITH READ LOCK statements in cases when there was a constant stream of concurrent DML statements (in two or more connections). This has happened because requests for protection against GRL which were acquired by DML statements were ignoring presence of pending GRL and thus the latter was starved. This patch solves both these problems by re-implementing GRL using metadata locks. Similar to the old implementation acquisition of GRL in new implementation is two-step. During the first step we block all concurrent DML and DDL statements by acquiring global S metadata lock (each DML and DDL statement acquires global IX lock for its duration). During the second step we block commits by acquiring global S lock in COMMIT namespace (commit code acquires global IX lock in this namespace). Note that unlike in old implementation acquisition of protection against GRL in DML and DDL is semi-automatic. We assume that any statement which should be blocked by GRL will either open and acquires write-lock on tables or acquires metadata locks on objects it is going to modify. For any such statement global IX metadata lock is automatically acquired for its duration. The first problem is solved because waits for GRL become visible to deadlock detector in metadata locking subsystem and thus deadlocks like one in the first bug become impossible. The second problem is solved because global S locks which are used for GRL implementation are given preference over IX locks which are acquired by concurrent DML (and we can switch to fair scheduling in future if needed). Important change: FTWRL/GRL no longer blocks DML and DDL on temporary tables. Before this patch behavior was not consistent in this respect: in some cases DML/DDL statements on temporary tables were blocked while in others they were not. Since the main use cases for FTWRL are various forms of backups and temporary tables are not preserved during backups we have opted for consistently allowing DML/DDL on temporary tables during FTWRL/GRL. Important change: This patch changes thread state names which are used when DML/DDL of FTWRL is waiting for global read lock. It is now either "Waiting for global read lock" or "Waiting for commit lock" depending on the stage on which FTWRL is. Incompatible change: To solve deadlock in events code which was exposed by this patch we have to replace LOCK_event_metadata mutex with metadata locks on events. As result we have to prohibit DDL on events under LOCK TABLES. This patch also adds extensive test coverage for interaction of DML/DDL and FTWRL. Performance of new and old global read lock implementations in sysbench tests were compared. There were no significant difference between new and old implementations.
196 lines
6.0 KiB
Plaintext
196 lines
6.0 KiB
Plaintext
# Copyright (c) 2008, 2010, Oracle and/or its affiliates. All rights reserved.
|
|
#
|
|
# This program is free software; you can redistribute it and/or modify
|
|
# it under the terms of the GNU General Public License as published by
|
|
# the Free Software Foundation; version 2 of the License.
|
|
#
|
|
# This program is distributed in the hope that it will be useful,
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
# GNU General Public License for more details.
|
|
#
|
|
# You should have received a copy of the GNU General Public License
|
|
# along with this program; if not, write to the Free Software Foundation,
|
|
# 51 Franklin Street, Suite 500, Boston, MA 02110-1335 USA
|
|
|
|
##
|
|
## WL#4814, 4.1.4 FILE IO
|
|
##
|
|
## Functional testing of File IO
|
|
##
|
|
|
|
--source include/not_embedded.inc
|
|
--source include/have_perfschema.inc
|
|
|
|
UPDATE performance_schema.SETUP_INSTRUMENTS SET enabled = 'NO', timed = 'YES';
|
|
|
|
UPDATE performance_schema.SETUP_INSTRUMENTS SET enabled = 'YES'
|
|
WHERE name LIKE 'wait/io/file/%';
|
|
|
|
--disable_warnings
|
|
DROP TABLE IF EXISTS t1;
|
|
--enable_warnings
|
|
|
|
#
|
|
# TODO: Change to InnoDB when it gets instrumentation
|
|
#
|
|
|
|
CREATE TABLE t1 (id INT PRIMARY KEY, b CHAR(100) DEFAULT 'initial value')
|
|
ENGINE=MyISAM;
|
|
|
|
INSERT INTO t1 (id) VALUES (1), (2), (3), (4), (5), (6), (7), (8);
|
|
|
|
TRUNCATE TABLE performance_schema.EVENTS_WAITS_HISTORY_LONG;
|
|
TRUNCATE TABLE performance_schema.EVENTS_WAITS_HISTORY;
|
|
TRUNCATE TABLE performance_schema.EVENTS_WAITS_CURRENT;
|
|
|
|
#
|
|
# FF1: Count for file should increase with instrumentation enabled and
|
|
# FF2: Count for file should not increase with instrumentation disabled
|
|
#
|
|
|
|
SELECT * FROM t1 WHERE id = 1;
|
|
|
|
SET @before_count = (SELECT SUM(TIMER_WAIT)
|
|
FROM performance_schema.EVENTS_WAITS_HISTORY_LONG
|
|
WHERE (EVENT_NAME = 'wait/io/file/myisam/dfile')
|
|
AND (OBJECT_NAME LIKE '%t1.MYD'));
|
|
|
|
SELECT IF(@before_count > 0, 'Success', 'Failure') has_instrumentation;
|
|
|
|
SELECT * FROM t1 WHERE id < 4;
|
|
|
|
SET @after_count = (SELECT SUM(TIMER_WAIT)
|
|
FROM performance_schema.EVENTS_WAITS_HISTORY_LONG
|
|
WHERE (EVENT_NAME = 'wait/io/file/myisam/dfile')
|
|
AND (OBJECT_NAME LIKE '%t1.MYD') AND (1 = 1));
|
|
|
|
SELECT IF((@after_count - @before_count) > 0, 'Success', 'Failure') test_ff1_timed;
|
|
|
|
UPDATE performance_schema.SETUP_INSTRUMENTS SET enabled='NO';
|
|
|
|
SET @before_count = (SELECT SUM(TIMER_WAIT)
|
|
FROM performance_schema.EVENTS_WAITS_HISTORY_LONG
|
|
WHERE (EVENT_NAME = 'wait/io/file/myisam/dfile')
|
|
AND (OBJECT_NAME LIKE '%t1.MYD') AND (2 = 2));
|
|
|
|
SELECT * FROM t1 WHERE id < 6;
|
|
|
|
SET @after_count = (SELECT SUM(TIMER_WAIT)
|
|
FROM performance_schema.EVENTS_WAITS_HISTORY_LONG
|
|
WHERE (EVENT_NAME = 'wait/io/file/myisam/dfile')
|
|
AND (OBJECT_NAME LIKE '%t1.MYD') AND (3 = 3));
|
|
|
|
SELECT IF((COALESCE(@after_count, 0) - COALESCE(@before_count, 0)) = 0, 'Success', 'Failure') test_ff2_timed;
|
|
|
|
#
|
|
# Check not timed measurements
|
|
#
|
|
|
|
UPDATE performance_schema.SETUP_INSTRUMENTS SET enabled = 'YES'
|
|
WHERE name LIKE 'wait/io/file/%';
|
|
|
|
UPDATE performance_schema.SETUP_INSTRUMENTS SET timed = 'NO';
|
|
|
|
TRUNCATE TABLE performance_schema.EVENTS_WAITS_HISTORY_LONG;
|
|
TRUNCATE TABLE performance_schema.EVENTS_WAITS_HISTORY;
|
|
TRUNCATE TABLE performance_schema.EVENTS_WAITS_CURRENT;
|
|
|
|
SELECT * FROM t1 WHERE id > 4;
|
|
|
|
SELECT * FROM performance_schema.EVENTS_WAITS_HISTORY_LONG
|
|
WHERE TIMER_WAIT != NULL
|
|
OR TIMER_START != NULL
|
|
OR TIMER_END != NULL;
|
|
|
|
SELECT * FROM performance_schema.EVENTS_WAITS_HISTORY
|
|
WHERE TIMER_WAIT != NULL
|
|
OR TIMER_START != NULL
|
|
OR TIMER_END != NULL;
|
|
|
|
SELECT * FROM performance_schema.EVENTS_WAITS_CURRENT
|
|
WHERE TIMER_WAIT != NULL
|
|
OR TIMER_START != NULL
|
|
OR TIMER_END != NULL;
|
|
|
|
UPDATE performance_schema.SETUP_INSTRUMENTS SET timed = 'YES';
|
|
|
|
SELECT * FROM t1 WHERE id < 4;
|
|
|
|
DROP TABLE t1;
|
|
|
|
#
|
|
# FF4: Use-case from Enterprise Monitor
|
|
#
|
|
|
|
--disable_result_log
|
|
SELECT SUM(COUNT_READ) AS sum_count_read,
|
|
SUM(COUNT_WRITE) AS sum_count_write,
|
|
SUM(SUM_NUMBER_OF_BYTES_READ) AS sum_num_bytes_read,
|
|
SUM(SUM_NUMBER_OF_BYTES_WRITE) AS sum_num_bytes_write
|
|
FROM performance_schema.FILE_SUMMARY_BY_INSTANCE
|
|
WHERE FILE_NAME LIKE CONCAT('%', @@tmpdir, '%') ORDER BY NULL;
|
|
--enable_result_log
|
|
|
|
#
|
|
# FF5: Troubleshooting tasks
|
|
#
|
|
# These queries will give different results based on timing,
|
|
# but at least they should not crash.
|
|
#
|
|
|
|
#
|
|
# Total and average wait time for different events on system level
|
|
#
|
|
--disable_result_log
|
|
SELECT EVENT_NAME, COUNT_STAR, AVG_TIMER_WAIT, SUM_TIMER_WAIT
|
|
FROM performance_schema.EVENTS_WAITS_SUMMARY_GLOBAL_BY_EVENT_NAME
|
|
WHERE COUNT_STAR > 0
|
|
ORDER BY SUM_TIMER_WAIT DESC
|
|
LIMIT 10;
|
|
--enable_result_log
|
|
|
|
#
|
|
# Total and average wait time for different users
|
|
#
|
|
|
|
## --disable_result_log
|
|
## SELECT i.user, SUM(TIMER_WAIT) SUM_WAIT
|
|
## # ((TIME_TO_SEC(TIMEDIFF(NOW(), i.startup_time)) * 1000) / SUM(TIMER_WAIT)) * 100 WAIT_PERCENTAGE
|
|
## FROM performance_schema.EVENTS_WAITS_HISTORY_LONG h
|
|
## INNER JOIN performance_schema.THREADS p USING (THREAD_ID)
|
|
## LEFT JOIN information_schema.PROCESSLIST i USING (ID)
|
|
## GROUP BY i.user
|
|
## ORDER BY SUM_WAIT DESC
|
|
## LIMIT 20;
|
|
## --enable_result_log
|
|
|
|
#
|
|
# Total and average wait times for different events for a session
|
|
#
|
|
--disable_result_log
|
|
SELECT h.EVENT_NAME, SUM(h.TIMER_WAIT) TOTAL_WAIT
|
|
FROM performance_schema.EVENTS_WAITS_HISTORY_LONG h
|
|
INNER JOIN performance_schema.THREADS p USING (THREAD_ID)
|
|
WHERE p.PROCESSLIST_ID = 1
|
|
GROUP BY h.EVENT_NAME
|
|
HAVING TOTAL_WAIT > 0;
|
|
--enable_result_log
|
|
|
|
#
|
|
# Which user reads and writes data
|
|
#
|
|
|
|
## --disable_result_log
|
|
## SELECT i.user, h.operation, SUM(NUMBER_OF_BYTES) bytes
|
|
## FROM performance_schema.EVENTS_WAITS_HISTORY_LONG h
|
|
## INNER JOIN performance_schema.THREADS p USING (THREAD_ID)
|
|
## LEFT JOIN information_schema.PROCESSLIST i USING (ID)
|
|
## GROUP BY i.user, h.operation
|
|
## HAVING BYTES > 0
|
|
## ORDER BY i.user, h.operation;
|
|
## --enable_result_log
|
|
|
|
# Clean-up.
|
|
UPDATE performance_schema.SETUP_INSTRUMENTS SET enabled = 'YES';
|