LOGICAL_CLOCK

[QFY]

System:CentOS 7.1
Package:mysql5.7.17

mysql configure:
slave_parallel_type=LOGICAL_CLOCK
slave_parallel_workers=0
log_bin=binlog
server=101
NO GTID mode

When I user xtrabackup backup mysql，
innobackup --defaults-file=/etc/my.cnf --user=muser --host=localhost --password=mpassword --slave-info --socket=/tmp/mysql.sock --port=3306 /backupdata/

When backup complete then copy to another server and apply log:
innobackup --apply-log /backupdata/2017-09-11_20_14_37/

then copy back:
innobackup --copy-back --defaults-file=/etc/my.cnf /backupdata/2017-09-11_20_14_37/

finally start mysql and change log,the log position is from the file:xtrabackup_slave_info

but when I change master and start slave,it says:
Could not execute Write_rows event on table table_schema.table_name; Duplicate entry '53589766' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log binlog.xxxx, end_log_pos 919535803

when uses:
slave_parallel_type=DATABASE
slave_parallel_workers=0
NO GTID mode

It works well;
It's that a issue? or something error?

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1474