Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.5
Description
http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-trusty-amd64/builds/17417
10.5 762bf7a03b6214f091a66ca8683df341 |
rpl.rpl_slave_alias_replica 'innodb,stmt' w4 [ fail ]
|
Test ended at 2020-06-12 09:52:25
|
|
CURRENT_TEST: rpl.rpl_slave_alias_replica
|
--- /usr/local/mariadb-10.5.4-linux-x86_64/mysql-test/suite/rpl/r/rpl_slave_alias_replica.result 2020-06-12 08:30:32.000000000 +0000
|
+++ /usr/local/mariadb-10.5.4-linux-x86_64/mysql-test/suite/rpl/r/rpl_slave_alias_replica.reject 2020-06-12 09:52:25.191267945 +0000
|
@@ -22,6 +22,7 @@
|
SHOW REPLICA HOSTS;
|
Server_id Host Port Master_id
|
2 127.0.0.1 SLAVE_PORT 1
|
+2 127.0.0.1 SLAVE_PORT 1
|
DROP USER 'repl_user';
|
connection slave;
|
"Command: SHOW SLAVE IO/SQL THREAD --> SHOW REPLICA IO/SQL THREAD"
|
|
mysqltest: Result length mismatch
|
The issue is not reproducible locally. The SHOW REPLICA HOSTS command reports an additional row for the same server occasionally.
This happens because of zombie dump threads on the master. SHOW REPLICA HOSTS goes through the list of dump threads and reports the corresponding hosts. Because of zombies it reports same host twice. Test needs to be improved.
Master's error log show this
2020-06-12 9:52:24 8 [Warning] Aborted connection 8 to db: 'unconnected' user: 'root' host: 'localhost' (A slave with the same server_uuid/server_id as this slave has co)