pt-stalk should use SQL_NO_CACHE
Bug #1318985 reported by
Kenny Gryp
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Fix Released
|
Medium
|
Frank Cizmich |
Bug Description
pt-stalk should use SQL_NO_CACHE when executing queries.
I had pt-stalks where most of the queries that were 'waiting on query cache mutex' were the pt-stalk queries (INNODB_TRX).
Ok, the query cache is a problem in this environment, but it skews up my stats I would get out of processlist and causes more threads_running spikes and potentially fails to obtain the necessary statistics in time.
Related branches
lp:~percona-toolkit-dev/percona-toolkit/pt-stalk-should-use-SQL_NO_CACHE-1318985
- Daniel Nichter: Approve
-
Diff: 34 lines (+5/-5)1 file modifiedbin/pt-stalk (+5/-5)
Changed in percona-toolkit: | |
status: | New → Confirmed |
Changed in percona-toolkit: | |
assignee: | nobody → Frank Cizmich (frank-cizmich) |
milestone: | none → 2.2.11 |
importance: | Undecided → Medium |
status: | Confirmed → In Progress |
Changed in percona-toolkit: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Added the SQL_NO_CACHE directive to the queries for locks and transactions
e.g:
SELECT SQL_NO_CACHE * FROM INFORMATION_ SCHEMA. INNODB_ LOCKS
etc