Extra lines in relay-log.info
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
||||
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.1 |
Won't Fix
|
High
|
Unassigned | |||
5.5 |
Triaged
|
High
|
Unassigned | |||
5.6 |
Triaged
|
High
|
Unassigned | |||
5.7 |
Triaged
|
High
|
Unassigned |
Bug Description
Currently relay-log.info file should have at most 7 lines, but if run test from upstream bug #25713 (http://
How to repeat.
Follow instructions from http://
1. Start replication
2. On master create a procedure:
mysql> \d |
mysql> create procedure p1()
-> BEGIN
-> DECLARE id INT;
-> set id=0;
-> while id<1000000 do
-> INSERT INTO test.tt VALUES (id);
-> set id=id+1;
-> end while;
-> END
-> |
Query OK, 0 rows affected (0.00 sec)
3. Run procedure few times:
call p1();
4. Create bash file:
#!/bin/bash
while [ 1 ]
do
cat /PATH/TO/
sleep 1
done
5. Run bash file
6. I don't see described corruption of line 4 as in original bug, but relay-log.info occasionally has 10 lines:
mysql> \! cat var/mysqld.
7
./slave-
69814314
master-bin.000009
69814150
0
0
1
0
1
mysql> \! cat var/mysqld.
10
Having that relay-log.info can have extra lines there is possibility it can be corrupted in worst way. Customer saw it corrupted binary log file name and position.
no longer affects: | percona-server/upstream-5.0 |
no longer affects: | percona-server/upstream-5.1 |
no longer affects: | percona-server/upstream-5.5 |
no longer affects: | percona-server/upstream-5.6 |
tags: | added: upstream |
This is easdy to confirm, there is no problem to see more than 7 lines in the relay-log.info on slave (I've used PS 5.6.25 and MySQL Sandbox) while procedure is running:
[openxs@chief node1]$ cat data/relay-log.info | wc -l sandbox21691- relay-bin. 000002
8
[openxs@chief node1]$ cat data/relay-log.info
7
./mysql_
451444
mysql-bin.000001
451281
0
0
1
[openxs@chief node1]$ cat data/relay-log.info | wc -l
8