Need error message with 'Skipping replication'

[Raghavendra D Prabhu]

For instance,

2014-06-23 17:30:15 17957 [Warning] WSREP: SQL statement was ineffective, THD: 26, buf: 119161
 QUERY: LOAD DATA INFILE '/tmp/gentest15902.tmp' INTO TABLE `table1000_innodb_compressed_key_pk_parts_4_int`
  => Skipping replication

is logged to error log. But, we don't know why it was skipped.

This is what is sent to client:

# 2014-06-23T17:30:15 [159# 2014-06-23T17:30:15 [15900] Query: LOAD DATA INFILE '/tmp/gentest15902.tmp' INTO TABLE `table1000_innodb_compressed_key_pk_parts_4_int` failed: 1213 Deadlock found when trying to get lock; try restarting transaction. Further errors of this kind will be suppressed.

It would be helpful to log the error to error log as well.

[Nilnandan Joshi (nilnandan-joshi)]

Confirmed. It didn't give the error that why it got skipped.

2015-05-25 14:10:01 1990 [ERROR] /usr/sbin/mysqld: Sort aborted: Lock wait timeout exceeded; try restarting transaction
2015-05-25 14:49:05 1990 [Warning] WSREP: SQL statement was ineffective, THD: 19, buf: 11578318
QUERY: drop table ip_test_table
 => Skipping replication

[Shahriyar Rzayev (rzayev-sehriyar)]

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