Description:
Typo in the output of:
"2019-07-11T18:00:17.795682Z 9 [Warning] file ./carlos-tutte-replication57-replication-1-bin.000011 was not purged because it was being readby thread number 2010 "
Notice there is a space missing between "read" and "by".
Checking the source code of latest 5.6 and 5.7 inside file sql/binlog.cc, it can be seen that as code was split in 2 lines, there is a space missing in between the words:
sql_print_warning("file %s was not purged because it was being read"
"by thread number %u", m_log_name, thd->thread_id());
How to repeat:
The typo can be checked by inspecting the source code.
If you need to check how the warning is printed on the error.log, execute:
on slave:
stop slave;
on master:
-- generate big binlog files
Then on both servers execute very fast:
on slave:
start slave;
on master:
SET GLOBAL max_binlog_files=1;
flush logs;
-- this will try to remove all binlogs except one. if slave is reading one, it won'be purged and the warning will be printed
Description: Typo in the output of: "2019-07-11T18:00:17.795682Z 9 [Warning] file ./carlos-tutte-replication57-replication-1-bin.000011 was not purged because it was being readby thread number 2010 " Notice there is a space missing between "read" and "by". Checking the source code of latest 5.6 and 5.7 inside file sql/binlog.cc, it can be seen that as code was split in 2 lines, there is a space missing in between the words: sql_print_warning("file %s was not purged because it was being read" "by thread number %u", m_log_name, thd->thread_id()); How to repeat: The typo can be checked by inspecting the source code. If you need to check how the warning is printed on the error.log, execute: on slave: stop slave; on master: -- generate big binlog files Then on both servers execute very fast: on slave: start slave; on master: SET GLOBAL max_binlog_files=1; flush logs; -- this will try to remove all binlogs except one. if slave is reading one, it won'be purged and the warning will be printed