Find Table Name using the table space id

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“.

Can’t auth ProxySQL with admin to 6032 when created user ‘admin’ under mysql_users table

This issue is the similar issue which is reported here 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 […]

Profile section is only visible on dashboard after new WordPress installation

After new installation of Wordpress once we login as wp-admin(administrator) account, We were only able to see the profile section at the left side of dashboard which is generally applicable to the subscriber role user profile.

Orchestrator: Master’s Read-Only Flag Checker

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.

Relay log read failure

Last_Errno: 1594
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.