Details
-
Bug
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
10.1.22
-
None
-
None
-
OS: Debian GNU/Linux 9.8 (stretch)
Description
Background:
- My cluster was M -> S replication(row-based), M crashed with some bug, see screenshot old_master_crash.png
- Then S was promoted to be new master
Description:
- A new slave instance was deployed by dba and data was loaded by mydumper&myloader from new master (standard operating procedure, works for all other failover scenario)
- All the things look good by command "SHOW SLAVE STATUS", however, only DDL can be applyed from relay log automaticlly, DML is not applyed anymore...
- All the things look good from replay log on slave, see screenshot "replay_log_on_new_slave.png"
- Only DDL can be found from slave binlog
- server_id is defferent between new master and new slave
- Tried to deploy a new slave, not working
- please see mysql config file "my-3313.cnf" of new slave with attachment
Kindly advise the probable cause and how to fix this promblem.