Change Details

db1114 is a host running buster+mariadb 10.3. Its MySQL is at: https://grafana.wikimedia.org/d/000000273/mysql?orgId=1&var-dc=eqiad%20prometheus%2Fops&var-server=db1114&var-port=9104&from=now-24h&to=now As it can be seen, there are some graphs that don't contain any data: * Monitoring queries latency * InnoDB Purge Lag * Change Buffer * Adaptive Hash and other memory usage * InnoDB Semaphores A possible explanation is that some metrics/options might have changed within `information_schema` and `performance_schema` on newer versions than 10.1 (the one we currently use in production) as we saw on {T231182} One of the blockers (apart from lots of more testing) is the fact that don't have full visibility at the moment on 10.3.

db1114 is a host running buster+mariadb 10.3. Its MySQL is at: https://grafana.wikimedia.org/d/000000273/mysql?orgId=1&var-dc=eqiad%20prometheus%2Fops&var-server=db1114&var-port=9104&from=now-24h&to=now As it can be seen, there are some graphs that don't contain any data: * Monitoring queries latency * InnoDB Purge Lag * Change Buffer * Adaptive Hash and other memory usage * InnoDB Semaphores A possible explanation is that some metrics/options might have changed within `information_schema` and `performance_schema` on newer versions than 10.1 (the one we currently use in production) as we saw on {T231182} One of the blockers (apart from lots of more testing) is the fact that don't have full visibility at the moment on 10.3. Update: the MySQL specific variables have been removed on 10.3 on upstream: https://jira.mariadb.org/browse/MDEV-18582

db1114 is a host running buster+mariadb 10.3. Its MySQL is at: https://grafana.wikimedia.org/d/000000273/mysql?orgId=1&var-dc=eqiad%20prometheus%2Fops&var-server=db1114&var-port=9104&from=now-24h&to=now As it can be seen, there are some graphs that don't contain any data: * Monitoring queries latency * InnoDB Purge Lag * Change Buffer * Adaptive Hash and other memory usage * InnoDB Semaphores A possible explanation is that some metrics/options might have changed within `information_schema` and `performance_schema` on newer versions than 10.1 (the one we currently use in production) as we saw on {T231182} One of the blockers (apart from lots of more testing) is the fact that don't have full visibility at the moment on 10.3. Update: the MySQL specific variables have been removed on 10.3 on upstream: https://jira.mariadb.org/browse/MDEV-18582