Reported by a customer that there was an error on the slave node with replication on the query_stats table. On CS, this table shouldnt be replicated because it keeps stats based on the UM its keep on.

So bin logging needs to ignore this table in the replication processing.

from master

Last_SQL_Error: Could not execute Write_rows_v1 event on table infinidb_querystats.querystats; Duplicate entry '817843' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log mysql-bin.000266, end_log_pos 4934

from one of the slave mysql error file:

2019-02-07 10:31:27 11 [ERROR] Slave SQL: Could not execute Write_rows_v1 event on table infinidb_querystats.querystats; Duplicate entry '817843' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log mysql-bin.000266, end_log_pos 4934, Gtid 0-1-5655754, Internal MariaDB error code: 1062