Query Cache support
Bug #1248089 reported by
Seppo Jaakola
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Low
|
Seppo Jaakola | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Query Cache has been declared as non-supported feature. The problem has been that high priority transactions (slave applier) could not get lock free access to query cache resources when invalidating query cache blocks or when aborting a victim possessing locks in query cache.
Related branches
Changed in codership-mysql: | |
status: | New → In Progress |
importance: | Undecided → Low |
assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
tags: | added: doc-rq |
tags: |
added: doc-req removed: doc-rq |
tags: | removed: doc-req |
To post a comment you must log in.
Tested Query Cache support in wsrep-5.6, and observed one unresolved deadlock when BF thread could not signal a victim, which was hanging in query cache end state. Fixed this deadlock and enabled query cache options in wsrep-5.6 revision: bazaar. launchpad. net/~codership/ codership- mysql/5. 6/revision/ 4007
http://