pt-stalk should use SQL_NO_CACHE

Bug #1318985 reported by Kenny Gryp
6
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.

Tags: pt-stalk
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
Revision history for this message
Frank Cizmich (frank-cizmich) wrote :

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

Changed in percona-toolkit:
status: In Progress → Fix Committed
Changed in percona-toolkit:
status: Fix Committed → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-648

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.