[MDEV-12744] Corrupted replication event was detected. Not printing the value Created: 2017-05-09  Updated: 2017-05-23  Resolved: 2017-05-22

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.1.23
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: hiller1 Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

10.1.23 enterprise

binlog_format = ROW

  1. mysqlbinlog mysql-bin.000001 --version
    mysqlbinlog Ver 3.3 for Linux at x86_64

Issue Links:
Duplicate
is duplicated by MDEV-5377 Row-based replication of MariaDB temp... Closed
is duplicated by MDEV-9567 mysqlbinlog fails to read binlog even... Closed

 Description    

mysqlbinlog -vv --base64-output=decode-rows mysql-bin.000001 | grep 'Corrupted' | more
 
###   @4=***Corrupted replication event was detected. Not printing the value***
 
###   @3=***Corrupted replication event was detected. Not printing the value***
 
###   @1=***Corrupted replication event was detected. Not printing the value***
 
###   @5=***Corrupted replication event was detected. Not printing the value***
 
###   @4=***Corrupted replication event was detected. Not printing the value***
 
###   @3=***Corrupted replication event was detected. Not printing the value***
 
###   @2=***Corrupted replication event was detected. Not printing the value***
 
###   @2=***Corrupted replication event was detected. Not printing the value***
 
###   @1=***Corrupted replication event was detected. Not printing the value***
 
###   @4=***Corrupted replication event was detected. Not printing the value***
 
###   @1=***Corrupted replication event was detected. Not printing the value***
 
###   @5=***Corrupted replication event was detected. Not printing the value***
 
###   @6=***Corrupted replication event was detected. Not printing the value***
 
###   @2=***Corrupted replication event was detected. Not printing the value***
 
###   @4=***Corrupted replication event was detected. Not printing the value***
 
###   @3=***Corrupted replication event was detected. Not printing the value***
 
###   @3=***Corrupted replication event was detected. Not printing the value***
 
###   @1=***Corrupted replication event was detected. Not printing the value***
 
###   @3=***Corrupted replication event was detected. Not printing the value***
 
###   @5=***Corrupted replication event was detected. Not printing the value***
 
###   @4=***Corrupted replication event was detected. Not printing the value***
 
###   @3=***Corrupted replication event was detected. Not printing the value***



 Comments   
Comment by hiller1 [ 2017-05-09 ] 

MariaDB [(none)]> show variables like '%binlog%';
 
+-----------------------------------------+----------------------+
 
| Variable_name                           | Value                |
 
+-----------------------------------------+----------------------+
 
| binlog_annotate_row_events              | OFF                  |
 
| binlog_cache_size                       | 1048576              |
 
| binlog_checksum                         | NONE                 |
 
| binlog_commit_wait_count                | 0                    |
 
| binlog_commit_wait_usec                 | 100000               |
 
| binlog_direct_non_transactional_updates | OFF                  |
 
| binlog_format                           | ROW                  |
 
| binlog_optimize_thread_scheduling       | ON                   |
 
| binlog_row_image                        | FULL                 |
 
| binlog_stmt_cache_size                  | 32768                |
 
| encrypt_binlog                          | OFF                  |
 
| gtid_binlog_pos                         | 0-148108-67364035    |
 
| gtid_binlog_state                       | 0-148108-67364035    |
 
| innodb_api_enable_binlog                | OFF                  |
 
| innodb_locks_unsafe_for_binlog          | OFF                  |
 
| max_binlog_cache_size                   | 18446744073709547520 |
 
| max_binlog_size                         | 134217728            |
 
| max_binlog_stmt_cache_size              | 18446744073709547520 |
 
| sync_binlog                             | 1                    |
 
| wsrep_forced_binlog_format              | NONE                 |
 
+-----------------------------------------+----------------------+

20 rows in set (0.00 sec)

Comment by Elena Stepanova [ 2017-05-09 ]

Can you provide the binlog?

Comment by hiller1 [ 2017-05-10 ] 

### UPDATE `test`.`info`
 
### WHERE
 
###   @1=663226 /* LONGINT meta=0 nullable=0 is_null=0 */
 
###   @2=8884749 /* LONGINT meta=0 nullable=0 is_null=0 */
 
###   @3='103201705070000533' /* VARSTRING(75) meta=75 nullable=0 is_null=0 */
 
###   @4=0 /* INT meta=0 nullable=1 is_null=0 */
 
###   @5=NULL /* INT meta=8 nullable=1 is_null=1 */
 
###   @6=NULL /* INT meta=0 nullable=1 is_null=1 */
 
###   @7=NULL /* INT meta=0 nullable=1 is_null=1 */
 
###   @8=NULL /* INT meta=150 nullable=1 is_null=1 */
 
###   @9=1463881305 /* TIMESTAMP meta=0 nullable=0 is_null=0 */
 
###   @10=1493172224 /* TIMESTAMP meta=0 nullable=0 is_null=0 */
 
###   @11=NULL /* TIMESTAMP meta=0 nullable=1 is_null=1 */
 
###   @12=76279718703842320 /* LONGINT meta=0 nullable=1 is_null=0 */
 
###   @13=NULL /* LONGINT meta=96 nullable=1 is_null=1 */
 
###   @14=NULL /* LONGINT meta=96 nullable=1 is_null=1 */
 
###   @15=NULL /* LONGINT meta=96 nullable=1 is_null=1 */
 
###   @16=NULL /* LONGINT meta=0 nullable=1 is_null=1 */
 
###   @17=NULL /* LONGINT meta=384 nullable=1 is_null=1 */
 
###   @18=NULL /* LONGINT meta=96 nullable=1 is_null=1 */
 
###   @19=NULL /* LONGINT meta=3072 nullable=1 is_null=1 */
 
###   @20=NULL /* LONGINT meta=0 nullable=1 is_null=1 */
 
###   @21=NULL /* LONGINT meta=96 nullable=1 is_null=1 */
 
### SET
 
###   @1=2214363594269655040 /* LONGINT meta=0 nullable=0 is_null=0 */
 
###   @2=-7922676169474834422 (10524067904234717194) /* LONGINT meta=0 nullable=0 is_null=0 */
 
###   @3=***Corrupted replication event was detected. Not printing the value***

Comment by Elena Stepanova [ 2017-05-12 ]

hiller1, I meant the actual binlog, as the file, not mysqlbinlog's interpretation of it.
If it's too big for an attachment or you don't want to make it public, you can upload it to ftp.askmonty.org/private.

Comment by hiller1 [ 2017-05-15 ]

I have uploaded to FTP. The file name is Corrupted_binlog_hiller1.tgz

THANKS

Comment by Elena Stepanova [ 2017-05-20 ]

Thank you.
You have indicated version 10.1.23, but the binary log actually says 10.0.25. Is it possible that you have replication from 10.0 to 10.1?
If so, possibly you have encountered the problem described in MDEV-5377 and issues linked to it. Does it look likely, given your configuration and table structures?

Comment by hiller1 [ 2017-05-22 ]

YES，I have replication from 10.0 to 10.1, 10.0 is master, 10.1 is slave, replicate is OK.

table structures：
`create_time` timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6),
`update_time` timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP(6),

10.0 insert result:
create_time
2017-05-22 00:00:49.000000
2017-05-22 00:01:04.000000
2017-05-22 00:01:27.000000

Comment by Elena Stepanova [ 2017-05-22 ]

Since the binary log was produced by 10.0 server, it is indeed the same problem as MDEV-5377 – or, more precisely, MDEV-9567, which has the same root cause as MDEV-5377.

You can track further progress in MDEV-5377.

Comment by hiller1 [ 2017-05-23 ]

THANKS!

Generated at Thu Feb 08 08:00:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.