Details
-
Bug
-
Status: Done
-
High
-
Resolution: Fixed
-
2.10.1
-
1
-
Platform Sprint 28
-
Yes
-
Yes
Description
Today one of our hosts was accidentally updated with yum update. As a result, pmm-agent was updated to 2.10 (server is 2.9.1). I started seeing those errors in logs:
Sep 15 19:53:04 cl2dbm101 pmm-agent[38891]: #033[36mINFO#033[0m[2020-09-15T19:53:04.428-07:00] time="2020-09-15T19:53:04-07:00" level=error msg="Error scraping for collect.custom_query.hr: mysql_perf_sche ma_replication_group:error running query on database: mysql_perf_schema_replication_group, Error 1054: Unknown column 'MEMBER_ROLE' in 'field list':mysql_perf_schema:error running query on database: mysql _perf_schema, Error 1054: Unknown column 'COUNT_TRANSACTIONS_REMOTE_IN_APPLIER_QUEUE' in 'field list':mysql_perf_schema_replication_group_worker:error running query on database: mysql_perf_schema_replicat ion_group_worker, Error 1054: Unknown column 'conn_status.LAST_QUEUED_TRANSACTION' in 'field list'" source="exporter.go:116" #033[36magentID#033[0m=/agent_id/db5953f1-c359-443c-b684-1a58cbddecfc #033[36m
Is it a result of combination 2.10 agent with 2.9 server? Or this is a bug in 2.10 agent?
Expectations:
- Group replication metrics should be for MySQL 8.0
- MySQL 5.7 and older should not have an error in logs and it's expected do not have GR metrics
