Aleksey,
can you switch back to perfschema and try to disable query examples?
we have theory that issue related to query examples.
Mykola, how can i “disable query examples”?
- Open “Query Analytics” interface
- choose database host
- click on SETTINGS button
- disable (uncheck) “Send real query examples” flag
- set “Collect from” field to “Performance Schema”
- click apply button
please notify me if any bugs still exists
You were right, it work fine with disabled “Send real query examples”
Is there some way to disable “Send real query examples” from command line? I just use ansible to add hosts to PMM, so i need to add it without GUI.
currently it is imposible to add node with disabled “Send real query examples” option.
but, I added such functionality as experimental feature (it is not reviewed and not tested) - [url]https://github.com/percona/pmm-client/pull/24[/url]
if you want you can compile it and test
sudo yum install golang git
mkdir /tmp/pmm-admin
cd /tmp/pmm-admin
git clone -b query-examples https://github.com/percona/pmm-client src/github.com/percona/pmm-client
export GOPATH=$(pwd)
go build ./src/github.com/percona/pmm-client/
sudo mv pmm-client /usr/sbin/pmm-admin
sudo pmm-admin remove mysql
sudo pmm-admin add mysql --disable-queryexamples
anyway it is workaround, we are searching root of the issue.
Hi Alexksey,
after all, I created the issue [url][PMM-589] capturing query examples from perf schema freezes the agent - Percona JIRA
feel free to add any additional information to jira ticket.
Ok, thanks.
Adventure does not end. Everything works fine, until slow_query_log disabled. In spite of the fact usage of performance_schema. Same problem, bad connection driver.
sorry, can you clarify one more time.
when slow_query_log=OFF, performance_schema=ON, query_examples=OFF, Do you have any issues?
Right now “slow_query_log=OFF, performance_schema=ON, query_examples=OFF”.
Problem exist.
A lot of WARNING in pmm-mysql-queries-0.log:
2017/02/17 08:51:00.001570 WARNING qan-analyzer-f122d8f8-worker Interval out of sequence: got 85, expected 81
2017/02/17 08:52:00.001470 WARNING qan-analyzer-f122d8f8 Skipping interval ‘86 2017-02-17 06:51:00 UTC to 2017-02-17 06:52:00 UTC (0-0)’ because interval ‘85 2017-02-17 06:50:00 UTC to 2017-02-17 06:51:00 UTC (0-0)’ is still being parsed
2017/02/17 08:53:00.001461 WARNING qan-analyzer-f122d8f8 Skipping interval ‘87 2017-02-17 06:52:00 UTC to 2017-02-17 06:53:00 UTC (0-0)’ because interval ‘85 2017-02-17 06:50:00 UTC to 2017-02-17 06:51:00 UTC (0-0)’ is still being parsed
2017/02/17 08:54:00.001591 WARNING qan-analyzer-f122d8f8 Skipping interval ‘88 2017-02-17 06:53:00 UTC to 2017-02-17 06:54:00 UTC (0-0)’ because interval ‘85 2017-02-17 06:50:00 UTC to 2017-02-17 06:51:00 UTC (0-0)’ is still being parsed
2017/02/17 08:55:00.001422 WARNING qan-analyzer-f122d8f8 Skipping interval ‘89 2017-02-17 06:54:00 UTC to 2017-02-17 06:55:00 UTC (0-0)’ because interval ‘85 2017-02-17 06:50:00 UTC to 2017-02-17 06:51:00 UTC (0-0)’ is still being parsed
2017/02/17 08:56:00.001660 WARNING qan-analyzer-f122d8f8-worker Interval out of sequence: got 90, expected 86
2017/02/17 08:57:00.001457 WARNING qan-analyzer-f122d8f8 Skipping interval ‘91 2017-02-17 06:56:00 UTC to 2017-02-17 06:57:00 UTC (0-0)’ because interval ‘90 2017-02-17 06:55:00 UTC to 2017-02-17 06:56:00 UTC (0-0)’ is still being parsed
After manipulation on settings page - switch to slowlog, switch to performance_schema, set and unset Send real query examples QAN start to work.
these warnings just warnings and shouldn’t affect qan-api functionality.
If i need to reinstall pmm-client, how do i have to clear all settings, caches, tampfiles etc after removing and before installing? Is there some place where all of this stored?
before reinstall please type pmm-admin uninstall on client side.
Ok, i removed, installed and configured client again, will see. Can i write here problems with grafana, or create other topic?
I think new topic is better
Well, for now QAN usable only with slow_query_log, not with performance_schema. Tested on 1.1.1 version.
what issues do you have with “performance_schema=ON, query_examples=OFF” ?