# query\_cache behaviour in multi-master mode for 5.6.21-70.1-56 **URL:** \ **Category:** Percona XtraDB Cluster 5.x\ **Created:** [January 19, 2015, 9:39am UTC](https://forums.percona.com/t/query-cache-behaviour-in-multi-master-mode-for-5-6-21-70-1-56/4001 "2015-01-19T09:39:27Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![marcel](https://avatars.discourse-cdn.com/v4/letter/m/71e660/32.png) [@marcel](https://forums.percona.com/u/marcel)\ **Post date:** [January 19, 2015, 9:39am UTC](https://forums.percona.com/t/query-cache-behaviour-in-multi-master-mode-for-5-6-21-70-1-56/4001/1 "2015-01-19T09:39:27Z")
The query\_cache is now supported in 5.6 but only after starting up. But i cannot find any reference to the node and cluster behaviour for a mult-master mode. ie is the query\_cache node or cluster specific and is there any cache invalidation across the nodes? For 5.5 i can find information about above, but not for 5.6 any help would be appreciated as my app is currently very depended on the query\_cache marcel ---
**Author:** ![przemek](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/przemek/32/3_2.png) [@przemek](https://forums.percona.com/u/przemek)\ **Post date:** [January 27, 2015, 3:23am UTC](https://forums.percona.com/t/query-cache-behaviour-in-multi-master-mode-for-5-6-21-70-1-56/4001/2 "2015-01-27T03:23:55Z")
The MySQL query\_cache is only node specific, there is no global cluster query cache. It works in the same way as on standalone MySQL instance, and there is no need for additional cluster-wide invalidation as any writes to tables referenced by a cached query will make it invalidated, so also the writes coming from replicated write sets. I would just like to remind that query cache may be beneficial in pretty not many production cases, hence many experts recommend this tuning: [url][http://dom.as/tech/query-cache-tuner/[/url]](http://dom.as/tech/query-cache-tuner/%5B/url%5D)