Data Monitoring / MySQL Monitoring
MySQL: Replica receiver versus applier
A replica receives changes but fails to apply them. Inspect replica status and worker errors, distinguishing retrieval progress from execution progress.
Environment and inputs: MySQL 8.4 baseline; Performance Schema consumers, privileges and replication topology affect evidence availability.
Failure scenario
A replica receives changes but fails to apply them. Confirm the cause before choosing a fix.
Evidence to collect
Inspect replica status and worker errors, distinguishing retrieval progress from execution progress. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Correct the specific applier failure with a consistency-aware recovery plan. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for replica receiver versus applier using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.