When I create a procedure on my master cluster in eu-west-1, my cross-region replica in eu-central-1 will start spewing errors to "error/mysql-error-running.log" like this:
[ERROR] Slave SQL: Error 'Access denied; you need (at least one of) the SUPER privilege(s) for this operation' on query. Default database: 'mydatabasename'. Query: 'CREATE DEFINER=`myusername`@`%` PROCEDURE `MyProcedureName`... (sql here)
2019-05-09 02:29:10 8118 [Warning] Slave: Access denied; you need (at least one of) the SUPER privilege(s) for this operation Error_code: 1227
2019-05-09 02:29:10 8118 [Warning] Slave: Access denied; you need (at least one of) the SUPER privilege(s) for this operation Error_code: 1227
2019-05-09 02:29:10 8118 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin-changelog.000016' position 24293051
Is there a way I can avoid this or just not replicate VIEWS or PROCEDURES to the cross-region replica?
When this happens my Cross-region replica breaks and stops replicating. I can call
CALL mysql.rds_skip_repl_error;
which sometimes gets me past it, but not always.
Note that this ONLY happens on cross-region replicas. Read replicas in the same cluster in my primary region (eu-west-1) do not have this problem at all.
Edited by: dtchadmyers on May 9, 2019 8:34 AM
