Data Monitoring / MySQL Monitoring
MySQL: Metadata lock waits
A schema change hangs behind an application transaction. Compare metadata lock evidence, active DDL and long transactions referencing the object.
Environment and inputs: MySQL 8.4 baseline; Performance Schema consumers, privileges and replication topology affect evidence availability.
Failure scenario
A schema change hangs behind an application transaction. Confirm the cause before choosing a fix.
Evidence to collect
Compare metadata lock evidence, active DDL and long transactions referencing the object. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Plan the schema change around actual lock dependencies and confirm rollback or cancellation behavior. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for metadata lock waits 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.