I am currently running a master - slave replication where on my slave there is an sql error due to which my replication was stopped.
when I tried to run the following good old solution
SHOW SLAVE STATUS \G; STOP SLAVE; SET GLOBAL sql_slave_skip_counter = 1; START SLAVE; SHOW SLAVE STATUS \G;
it didn't work. The
Skip_Counter shows a value of 1 but when I again ran
SHOW SLAVE STATUS the value was decreased to 0 but the error was still there. Along with that,
Exec_Master_Log_Pos doesn't change.
is there any thing wrong with my expectation ?
Error is as follows:
Error 'String 'abcde_abcdefgh_abcd' is too long for user name (should be no longer than 16)' on query. Default database: ''. Query: 'GRANT SELECT ON mydb.* TO 'abcde_abcdefgh_abcd'@'192.168.1.4' IDENTIFIED WITH 'mysql_native_password' AS 'PASSWORD_HASH'
My Master version is
5.7 and that on slave is
5.6. Upgrading the slave did solve the problem as the query could be executed on slave as well but my question is still there. Why couldn't skip counter solve the replication blockage ?