Bug #76850 Duplicate delete query in MySQL master binary log
Submitted: 27 Apr 2015 11:36 Modified: 28 Apr 2015 11:37
Reporter: kamal sharma Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Replication Severity:S2 (Serious)
Version:5.6 OS:Any
Assigned to: CPU Architecture:Any

[27 Apr 2015 11:36] kamal sharma
Description:
We are facing strange problem, while replication data from master to slave. Same data is being deleted twice in log(How ever only one row is deleted and one time),due to which we are getting error while replication.

    # at 28651234
    #150423 12:21:03 server id 5170  end_log_pos 28651303 CRC32 0x0b496431  Delete_rows: table id 73 flags: STMT_END_F
    ### DELETE FROM `oauth`.`AccessToken_scopes`
    ### WHERE
    ###   @1=1040103520
    ###   @2='wallet'
    ### DELETE FROM `oauth`.`AccessToken_scopes`
    ### WHERE
    ###   @1=1040103520
    ###   @2='wallet'

To avoid this,we currently have added below parameter in `my.cnf` file.

    slave-skip-errors

Mysql version :- 5.6 
Storage : InnoDB Engine

How to repeat:
We are facing strange problem, while replication data from master to slave. Same data is being deleted twice in log(How ever only one row is deleted and one time),due to which we are getting error while replication.

    # at 28651234
    #150423 12:21:03 server id 5170  end_log_pos 28651303 CRC32 0x0b496431  Delete_rows: table id 73 flags: STMT_END_F
    ### DELETE FROM `oauth`.`AccessToken_scopes`
    ### WHERE
    ###   @1=1040103520
    ###   @2='wallet'
    ### DELETE FROM `oauth`.`AccessToken_scopes`
    ### WHERE
    ###   @1=1040103520
    ###   @2='wallet'

To avoid this,we currently have added below parameter in `my.cnf` file.

    slave-skip-errors

Mysql version :- 5.6 
Storage : InnoDB Engine
[27 Apr 2015 11:42] kamal sharma
updated version
[28 Apr 2015 7:47] MySQL Verification Team
Thank you for the report.
Could you please provide conf file/full error log from both master/slave, exact MySQL version and exact schema(SHOW CREATE TABLE <table_name>\G, any triggers used etc) with sample data which causing issue?

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.
[28 Apr 2015 11:37] kamal sharma
Here below in the configuration.

Mysql version --> 5.6.22

Show create table :-->

CREATE TABLE `token` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `creation_date` datetime DEFAULT NULL,
  `modification_date` datetime DEFAULT NULL,
  `expires` bigint(20) DEFAULT NULL,
  `userId` varchar(255) DEFAULT NULL,
  `token` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `U_CCSSTKN_TOKEN` (`token`),
  KEY `token_resourceOwnerId` (`userId`),
  KEY `idx_token_expiry` (`expires`),
  KEY `idx_mdt` (`modificationDate`)
) ENGINE=InnoDB AUTO_INCREMENT=65434 DEFAULT CHARSET=utf8 

CREATE TABLE `AccessToken_scopes` (
  `token_id` bigint(20) DEFAULT NULL,
  `element` varchar(255) DEFAULT NULL,
  KEY `I_CCSSCPS_ACCESSTOKEN_ID` (`ACCESSTOKEN_ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
[29 Apr 2015 9:48] MySQL Verification Team
Could you please provide conf file/full error log from both master/slave?Also, sample data(for the tables involved) to trigger this issue? If you prefer then mark the note as private etc

Thanks,
Umesh