mirror of
https://github.com/MariaDB/server.git
synced 2025-10-25 17:08:14 +02:00
10ebdb7f1d
Problem:
=======
Executing command, "mysqlbinlog --read-from-remote-server --host='xx.xx.xx.xx'
--port=3306 --user=xxx --password=xxx --database=mysql --to-last-log
mysql-bin.000001 --start-position=1098699 --stop-never |mysql -uxxx -pxxx", we
found that last data read from remote couldn't commit.
Analysis:
========
The purpose of 'Write_on_release_cache' is that the contents of the Cache will
automatically be written to a dedicated result file on destruction. Flush
operation on the result file is controlled by a flag 'FLUSH_F'. Events which
require force flush upon their destruction will have to enable this
'Write_on_release_cache::FLUSH_F'. At present the 'FLUSH_F' flag is defined as
an enum as shown below.
enum flag
{
FLUSH_F
};
Since 'FLUSH_F' is the first member without initialization it get the default
value '0'. Because of this the following flush condition never succeeds.
if (m_flags & FLUSH_F)
fflush(m_file);
At present the file gets flushed only during my_fclose(result_file) operation.
When continuous streaming is enabled through --stop-never option it never gets
flushed and hence events are not replicated.
Fix:
===
Initialize the enum value to non zero value.
16 lines
585 B
Text
16 lines
585 B
Text
RESET MASTER;
|
|
include/stop_dump_threads.inc
|
|
# Step-1: Execute some dummy statements.
|
|
CREATE TABLE t1(i int);
|
|
INSERT INTO t1 values (1);
|
|
# Step-2: Disable binary log temporarily and drop the table 't1'.
|
|
set @@SESSION.SQL_LOG_BIN = 0;
|
|
DROP TABLE t1;
|
|
set @@SESSION.SQL_LOG_BIN = 1;
|
|
# Step-3: Execute MYSQL_BINLOG with --stop-never and source it to mysql client.
|
|
# Step-4: Wait till dump thread transfer is completed.
|
|
# Step-5: Check that the data is there.
|
|
# Step-6: Cleanup
|
|
# kill the dump thread serving the mysqlbinlog --stop-never process
|
|
include/stop_dump_threads.inc
|
|
DROP TABLE t1;
|