EC
1750
MariaDBERRORCommonReplicationHIGH confidence

Failed to change replication info repository

Production Risk

High — replication configuration change failed.

What this means

MySQL failed to switch the replication information repository type (e.g., from FILE to TABLE) due to an internal error.

Why it happens
  1. 1Existing replication data is inconsistent or locked.
  2. 2Insufficient privileges to create the mysql.slave_master_info or mysql.slave_relay_log_info tables.
How to reproduce
trigger — this will error
trigger — this will error
SET GLOBAL master_info_repository = 'TABLE'; -- fails if current state is inconsistent

expected output

ERROR 1750 (HY000): Failed to change the type of master_info_repository.

Fix

Stop replication, reset, and retry

Stop replication, reset, and retry
STOP SLAVE;
RESET SLAVE ALL;
SET GLOBAL master_info_repository = 'TABLE';
CHANGE MASTER TO ...;

Why this works

Clears stale replication state before switching repository type.

What not to do

✕

Sources
Official documentation ↗

MySQL 8.0 — 1750 ER_CHANGE_RPL_INFO_REPOSITORY_FAILURE

Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev

← All MariaDB errors