Are these queries actually slow (long run time) or are they notifying about full table scans? What is your slow query log related MySQL configuration?
The latter happens e.g. when you have many connections open (long `information_schema.processlist`). These MySQL-internal tables are in-memory or not really materialized in any form at all, so they do not have any indexes; any query is a full table scan. This is okay because they are not materialized anyway. However, MySQL has a threshold for what it considers "too many rows to do a full table scan" and logs a slow query when that is exceeded. /MR On Thu, Sep 3, 2020 at 3:30 PM [email protected] <[email protected]> wrote: > We're trying to use mysqld_exporter for monitoring performance and at some > moments it's causing slow running queries. Some tables are reaching 10-20G > in size so that could be one of the reasons. Is there a way to prevent such > queries? > > -- > You received this message because you are subscribed to the Google Groups > "Prometheus Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/prometheus-users/45ac56cd-aba5-430f-b61a-94cdec02540dn%40googlegroups.com > <https://groups.google.com/d/msgid/prometheus-users/45ac56cd-aba5-430f-b61a-94cdec02540dn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/CAMV%3D_gasXsx28RyffivBOFHUft2fn_JGoUKvPnjQhfdfk2Wb5A%40mail.gmail.com.
