Reason: Unable to migrate database to Aurora. Some of the tables in this snapshot are corrupted. Please try migrating a different snapshot or dump and load to a new database and try to migrate.
Got fatal error 1236 from master when reading data from binary log: ‘The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. Replicate the missing transactions from elsewhere, or provision a new slave from backup. Consider increasing the master’s binary log expiration period. The GTID set sent by the slave is ‘00019832-1111-1111-1111-111111111111:1,
00019832-1111-1111-2222-111111111111:1’, and the missing transactions are ‘00019832-1111-1111-2222-111111111111:10′.’
Here we are going to share a SQL query to find the table name based on the space id logged inside the error log. Suppose We have some below error logged inside the error log file. From above error log, we can find the table name using the “space=107“.
This issue is the similar issue which is reported here https://github.com/sysown/proxysql/issues/1538. I found some workaround to fix this issue, without initialising or recreate/reconfigure your ProxySQL node. Problem: We have default ProxySQL user “admin” to connect the ProxySQL over the 6032 port. Once we connected and created the “admin” user account inside the mysql_users table and […]
Here in this blog post, you will understand the steps to install, configure and perform the failover for Orchestrator tool.
Here We know the orchestrator takes care of read-only flag once we perform the failovers. but suppose our master node’s MySQL service is restarted due to accidentally or crash or OOM issue then once the MySQL service will be up on the master node, we will have to manually connect the node and disable the read-only flag, so the application can resume their write hits.
Last_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the relay log), a network problem, or a bug in the master’s or slave’s MySQL code. If you want to check the master’s binary log or slave’s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS’ on this slave.