Exact

Exact Union RegExp

Kristian Nielsen 53468695ad MDEV-38776 [ERROR] Slave worker thread retried transaction 10 time(s) in vain, giving up ... Partially revert this commit: commit 6a1cb449fe Author: Sergei Golubchik <serg@mariadb.org> Date: Mon Jan 18 18:02:16 2021 +0100 cleanup: remove slave background thread, use handle_manager thread instead This restores running the parallel replication deadlock killing in its own dedicated thread, not in the manager thread shared with other unrelated processing. When a parallel replication conflict is detected, multiple threads can be waiting for each other, potentially in a loop. It is critical for correctness (as well as performance) that the blocking thread is killed immediately to allow other threads to continue. If one of the threads being blocked was the manager thread itself in some unrelated job, the kill could end up being blocked indefinitely, causing replication to hang, usually eventually timing out on innodb_lock_wait_timeout and failing replication with an error like: [ERROR] Slave worker thread retried transaction 10 time(s) in vain, giving up Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>		2026-02-09 02:11:23 +01:00
..
include	MDEV-9077 - sysschema test suite.	2021-03-18 08:02:48 +01:00
r	MDEV-38776 [ERROR] Slave worker thread retried transaction 10 time(s) in vain, giving up	2026-02-09 02:11:23 +01:00
t	Merge branch 10.11 into 11.4	2025-09-02 15:58:39 +02:00
disabled.def	Merge 10.5 into 10.6	2023-12-19 18:41:42 +02:00
suite.opt	MDEV-9077 - sysschema test suite.	2021-03-18 08:02:48 +01:00
suite.pm	MDEV-9077 - sysschema test suite.	2021-03-18 08:02:48 +01:00