I have a MariaDB 10.3 Galera slave node with general logging turned on. It's consuming binlogs generated by a MySQL 5.5 NDB cluster. The binlog format is row-based in both databases.
SHOW ALL SLAVES STATUS; indicates that
Exec_Master_Log_Pos are caught up to the position on the master DB,
Seconds_Behind_Master is 0, and no errors are logged.
Making an INSERT/UPDATE/DELETE on the master database immediately causes the following entries in the slave's general log:
190412 21:02:04 74 Query BEGIN
74 Query COMMIT
Additionally, the Read and Exec positions will tick upwards,
Executed_log_entries will increase, and the relay binlog will get a new entry. Every metric and status indicator I know of suggests that the slave believes it's replicating, but the data doesn't replicate. DDL statements do replicate, however.
There are no filtering rules of any kind on the master/slave nodes.
Replicate_Wild_Ignore_Table are all empty.
Where do I even start troubleshooting this? What could cause the slave to silently fail to replicate?