Failure Reasons

Last updated: 2020-02-20 12:31:37

    The number of tables in a single instance exceeds 1 million

    When the number of tables in a single instance exceeds 1 million, it may cause backup failure and affect database monitoring. Please regulate the number of tables reasonably and control the number of tables in a single instance to no more than 1 million.

    Large transactions caused by non-primary key tables

    Cause analysis

    When there is no primary key table in the instance and the binlog is in row format, when a sql updates / deletes a large amount of data, playback on the slave machine will cause a large transaction, resulting in the backup thread unable to acquire the lock, resulting in backup failure.

    Treatment scheme

    1. Check all the non-primary key tables that exist in the instance through sql.
    select TABLE_SCHEMA,TABLE_NAME,TABLE_TYPE,ENGINE,TABLE_ROWS from information_schema.tables where (table_schema,table_name) not in (select table_schema,table_name from information_schema.columns where COLUMN_KEY='PRI') and table_schema not in ('sys','mysql','information_schema','performance_schema');
    1. Add a primary key to a table without a primary key.
    alter table table_name add primary key(`column_name`);

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback
    Help