default monitoring-schema=false because we don't wan't to impact any big user with 30K of tables
In such situation we should detect at least the missing for replication_manager_schema when we change settings or call an api that may use it or depend on it
I would suggest to have monitoring-schema =on
monitoring-schema-level=1 (database only )
monitoring-schema-level=2 (database and table if table count < monitoring-schema-max-tables ) (default)
monitoring-schema-level=3 (all tables)
monitoring-schema-check-level = 1 missing object
monitoring-schema-check-level = 2 metadata diff
monitoring-schema-check-level = 3 rowcount
monitoring-schema-check-level = 4 random content checksum
monitoring-schema-random-checksum-per-sec = 10
Confirme that it does not produce order by or so in the information_schema and produce temporary table on disk
may be using MAriaDB SQL handler interface can be good for fetching table in
default monitoring-schema=false because we don't wan't to impact any big user with 30K of tables In such situation we should detect at least the missing for replication_manager_schema when we change settings or call an api that may use it or depend on it
I would suggest to have monitoring-schema =on monitoring-schema-level=1 (database only ) monitoring-schema-level=2 (database and table if table count < monitoring-schema-max-tables ) (default) monitoring-schema-level=3 (all tables) monitoring-schema-check-level = 1 missing object monitoring-schema-check-level = 2 metadata diff monitoring-schema-check-level = 3 rowcount monitoring-schema-check-level = 4 random content checksum monitoring-schema-random-checksum-per-sec = 10
Confirme that it does not produce order by or so in the information_schema and produce temporary table on disk
may be using MAriaDB SQL handler interface can be good for fetching table in
Dbjob Toggle traffic