Bug #105234 | START SLAVE UNTIL SQL_AFTER_GTIDS Does not Stop When Past GTID | ||
---|---|---|---|
Submitted: | 15 Oct 2021 0:58 | Modified: | 27 Oct 2021 19:53 |
Reporter: | Jervin Real | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 8.0.26 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[15 Oct 2021 0:58]
Jervin Real
[25 Oct 2021 11:42]
MySQL Verification Team
Hi Jervin, I'm having issue reproducing this. What's the content of your master/my.sandbox.cnf and node#/my.sandbox.cnf ? thanks
[25 Oct 2021 21:18]
Jervin Real
Hi, Configs are basically defaults generated by dbdeployer. This master/my.sandbox.cnf [mysql] prompt='master [\h:21627] {\u} (\d) > ' # [client] user = msandbox password = msandbox port = 21627 socket = /tmp/mysql_sandbox21627.sock [mysqld] user = jervin port = 21627 socket = /tmp/mysql_sandbox21627.sock basedir = /home/jervin/opt/mysql/8.0.26 datadir = /home/jervin/sandboxes/rsandbox_8_0_26/master/data tmpdir = /home/jervin/sandboxes/rsandbox_8_0_26/master/tmp pid-file = /home/jervin/sandboxes/rsandbox_8_0_26/master/data/mysql_sandbox21627.pid bind-address = 127.0.0.1 report-host = node-1 report-port=21627 log-error=/home/jervin/sandboxes/rsandbox_8_0_26/master/data/msandbox.err server-id=100 # basic replication options relay-log-index=mysql-relay relay-log=mysql-relay log-bin=mysql-bin mysqlx-port=31627 mysqlx-socket=/tmp/mysqlx-31627.sock And this is one of the replicas: [mysql] prompt='slave1 [\h:21628] {\u} (\d) > ' # [client] user = msandbox password = msandbox port = 21628 socket = /tmp/mysql_sandbox21628.sock [mysqld] user = jervin port = 21628 socket = /tmp/mysql_sandbox21628.sock basedir = /home/jervin/opt/mysql/8.0.26 datadir = /home/jervin/sandboxes/rsandbox_8_0_26/node1/data tmpdir = /home/jervin/sandboxes/rsandbox_8_0_26/node1/tmp pid-file = /home/jervin/sandboxes/rsandbox_8_0_26/node1/data/mysql_sandbox21628.pid bind-address = 127.0.0.1 report-host = node-2 report-port=21628 log-error=/home/jervin/sandboxes/rsandbox_8_0_26/node1/data/msandbox.err server-id=200 # basic replication options relay-log-index=mysql-relay relay-log=mysql-relay log-bin=mysql-bin mysqlx-port=31628 mysqlx-socket=/tmp/mysqlx-31628.sock
[27 Oct 2021 19:53]
MySQL Verification Team
Thanks for the report
[19 Jan 2022 2:01]
MySQL Verification Team
Hi, One thing my colleague from dev team noticed that we would like to doublecheck: In the 'How to repeat' steps, looks like you used a different server-uuid in start 'slave until SQL_BEFORE_GTIDS' command. slave1 [localhost:21628] {msandbox} ((none)) > show slave status \G *************************** 1. row *************************** ... Master_Server_Id: 21627 Master_UUID: **00021627**-1111-1111-1111-111111111111 Master_Info_File: mysql.slave_master_info SQL_Delay: 0 SQL_Remaining_Delay: NULL Slave_SQL_Running_State: Replica has read all relay log; waiting for more updates ... Retrieved_Gtid_Set: **00021627**-1111-1111-1111-111111111111:1-33 Executed_Gtid_Set: **00021627**-1111-1111-1111-111111111111:1-33 Auto_Position: 1 ... 1 row in set, 1 warning (0.00 sec) slave1 [localhost:21628] {msandbox} ((none)) > stop slave; start slave until SQL_BEFORE_GTIDS = '**00020135**-1111-1111-1111-111111111111:10'; Could you please confirm the difference in server-uuid is intentional or a mistake? Is this mistake copy/pasting from different reproduction turns or something else Thanks