Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL)
-
None
Description
rpl.rpl_parallel_optimistic 'innodb,stmt' w2 [ fail ]
|
Test ended at 2018-02-06 20:43:04
|
|
|
CURRENT_TEST: rpl.rpl_parallel_optimistic
|
mysqltest: In included file "./include/sync_with_master_gtid.inc":
|
included from /usr/share/mysql-test/suite/rpl/t/rpl_parallel_optimistic.test at line 306:
|
At line 48: Failed to sync with master
|
|
|
The result from queries just before the failure was:
|
< snip >
|
7 5
|
8 7
|
9 8
|
10 8
|
SELECT * FROM t2 ORDER BY a;
|
a b
|
1 0
|
2 0
|
4 4
|
5 5
|
6 5
|
7 7
|
8 7
|
9 8
|
10 10
|
include/save_master_gtid.inc
|
connection server_2;
|
include/start_slave.inc
|
include/sync_with_master_gtid.inc
|
Timeout in master_gtid_wait('0-1-88', 120), current slave GTID position is: 0-1-87.
|
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- relates to
-
-
- Closed
-
Activity
the failure still happens -
on 10.5 http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64-debug/builds/4776/steps/mtr/logs/stdio
rpl.rpl_parallel_optimistic 'innodb,mix' w3 [ fail ]
|
Test ended at 2020-08-26 06:00:15
|
|
|
CURRENT_TEST: rpl.rpl_parallel_optimistic
|
mysqltest: In included file "./include/sync_with_master_gtid.inc":
|
included from /usr/share/mysql-test/suite/rpl/t/rpl_parallel_optimistic.test at line 315:
|
At line 48: Failed to sync with master
|
|
|
The result from queries just before the failure was:
|
< snip >
|
7 5
|
8 7
|
9 8
|
10 8
|
SELECT * FROM t2 ORDER BY a;
|
a b
|
1 0
|
2 0
|
4 4
|
5 5
|
6 5
|
7 7
|
8 7
|
9 8
|
10 10
|
include/save_master_gtid.inc
|
connection server_2;
|
include/start_slave.inc
|
include/sync_with_master_gtid.inc
|
Timeout in master_gtid_wait('0-1-88', 120), current slave GTID position is: 0-1-77.
|
|
|
More results from queries before failure can be found in /dev/shm/var/3/log/rpl_parallel_optimistic.log
|
This is almost certainly a duplicate of MDEV-28776 / MDEV-31655.
The test is a plain parallel replication of a batch of conflicting INSERT ... SELECT. And the server error log shows that these fail with deadlock error and more than 10 retries needed.
2023-07-14 21:23:16 86 [ERROR] Slave worker thread retried transaction 10 time(s) in vain, giving up. Consider raising the value of the slave_transaction_retries variable.
|
2023-07-14 21:23:16 86 [Warning] Slave: Deadlock found when trying to get lock; try restarting transaction Error_code: 1213
|
2023-07-14 21:23:16 85 [Warning] Slave: Connection was killed Error_code: 1927
|
The case looks as relating to
MDEV-12746rpl.rpl_parallel_optimistic_nobinlog fails committing out of order at retry. Could be as well be a duplicate.The failure happens in a similar block of the supposed parent bug: 10 worker threads may not complete
execution of the INSERTs on ll:276..297 because of a glitch in temp failure retrying that
MDEV-12746is fixing.