Database metric/command drift
MySQL 8.4 SHOW SLAVE STATUS removed SHOW REPLICA STATUS documentation
Monitoring/automation cannot inspect replication state.
Agent Quick Fix
Repair against the current MySQL 8.4 contract, then keep the change narrow and source-backed.
Product: MySQL 8.4
Current-contract area: SHOW SLAVE STATUS removed
Likely root cause: Monitoring/automation cannot inspect replication state.
Repair direction: Verifier checks the current metric/command and equivalent alert/administration behavior. Check operational state and security, not a compatibility switch that weakens the server.Symptom
Monitoring/automation cannot inspect replication state.
Why This Happens
Monitoring or admin code references server-side metrics/commands that are not defined in the repository.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
MySQL 8.4 SHOW SLAVE STATUS removed SHOW REPLICA STATUS documentation
site:dev.mysql.com MySQL 8.4 SHOW SLAVE STATUS SHOW REPLICA STATUS
https://dev.mysql.com/doc/refman/8.4/en/show-replica-status.html