# Gcache.page.\* files constantly generated on the PXC 5.6.51

**URL:** <https://forums.percona.com/t/gcache-page-files-constantly-generated-on-the-pxc-5-6-51/16221>\
**Category:** Percona XtraDB Cluster 5.x\
**Tags:** percona\
**Created:** [June 20, 2022, 8:34pm UTC](https://forums.percona.com/t/gcache-page-files-constantly-generated-on-the-pxc-5-6-51/16221 "2022-06-20T20:34:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![msutic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/msutic/32/4218_2.png) [@msutic](https://forums.percona.com/u/msutic)\
**Post date:** [June 20, 2022, 8:34pm UTC](https://forums.percona.com/t/gcache-page-files-constantly-generated-on-the-pxc-5-6-51/16221/1 "2022-06-20T20:34:50Z")

</div>

Hello,

We have a 3-node Percona XTraDB Galera Cluster configuration:

```auto
5.6.51-91.0-56-log 
wsrep_provider_version=3.46(r0ef0d79) 
gcache.size = 1G

```

Files “gcache.page.\*” are generated almost every minute and not cleaned which causes high disk space usage. To overcome issue we need to shutdown service and delete files manually.

I don’t see big transactions (large write-sets) which should trigger creation of the gcache.page.\* files. Parameter gcache.keep\_pages\_count does not have any effect on the file generation/retention.

Has anybody had similar experiences with generating “gcache.page.\*” files?  
How to troubleshoot or resolve this issue?

p.s.  
I understand that 5.6 is very old version and that we should upgrade, but still if anybody has any (other) advice I would be grateful.

Best regards,  
Marko

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [June 20, 2022, 8:43pm UTC](https://forums.percona.com/t/gcache-page-files-constantly-generated-on-the-pxc-5-6-51/16221/2 "2022-06-20T20:43:16Z")

</div>

Hello @msutic,  
Unfortunately, 5.6 is dead, EOL’d. Any bugs discovered won’t get fixed. There have been many improvements in the Galera library not only between 5.6-\>5.7, but also from 5.7-\>8.0. Your best, and honestly, only option, is to upgrade to latest 5.7.\* and verify the issue still exists.

---

<div class="post-metadata">

**Author:** ![msutic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/msutic/32/4218_2.png) [@msutic](https://forums.percona.com/u/msutic)\
**Post date:** [June 22, 2022, 4:22am UTC](https://forums.percona.com/t/gcache-page-files-constantly-generated-on-the-pxc-5-6-51/16221/3 "2022-06-22T04:22:57Z")

</div>

Thank you for the answer.  
We plan upgrade from 5.6 in the near future but till then need to solve issues on 5.6.

It looks like problem with generating gcache.page\* files is solved resizing gcache 1GB → 5GB.  
We’ll see now after a few days.

Best regards,  
Marko

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [June 22, 2022, 12:19pm UTC](https://forums.percona.com/t/gcache-page-files-constantly-generated-on-the-pxc-5-6-51/16221/4 "2022-06-22T12:19:44Z")

</div>

Take a look at this post that explains the behavior you are seeing: [All You Need to Know About GCache (Galera-Cache) - Percona Database Performance Blog](https://www.percona.com/blog/2016/11/16/all-you-need-to-know-about-gcache-galera-cache/)

---

<div class="post-metadata">

**Author:** ![msutic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/msutic/32/4218_2.png) [@msutic](https://forums.percona.com/u/msutic)\
**Post date:** [June 24, 2022, 6:41am UTC](https://forums.percona.com/t/gcache-page-files-constantly-generated-on-the-pxc-5-6-51/16221/5 "2022-06-24T06:41:06Z")

</div>

I have seen this document and this is why I decided to go with larger gcache.  
Still, this behavior does not look good to me. We don’t have so big transactions (write-sets) to cause allocation of additional pages few times per minute.  
Also **gcache.keep\_pages\_size** does not have any effect on the number of this files.

But, we are on a very old version ant it is best to upgrade and not to troubleshoot further.  
We have found a solution (large gcache) and this is good enough for now.