Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documented "gcache" config contradicts advice, cleanup is missing #137

Open
ayurchen opened this issue Dec 1, 2015 · 6 comments
Open

Documented "gcache" config contradicts advice, cleanup is missing #137

ayurchen opened this issue Dec 1, 2015 · 6 comments
Labels

Comments

@ayurchen
Copy link
Member

ayurchen commented Dec 1, 2015

Migrated from codership/galera#373

Customer is using Galera 3.25 with MySQL 5.6.23:
galera-3-25.3.10-2.el6.x86_64
mysql-wsrep-client-5.6-5.6.23-25.10.el6.x86_64
mysql-wsrep-5.6-5.6.23-25.10.el6.x86_64
mysql-wsrep-server-5.6-5.6.23-25.10.el6.x86_64

Customer followed config example on page "http://galeracluster.com/documentation-webpages/configuration.html":

wsrep_provider_options="gcache.size=300M; gcache.page_size=1G"

"gcache" cleanup doesn't work, 148 gcache pages of 1 GB each have accumulated since Sep 2.
Customer is approaching "disk full" and must take action.

In chat communication, I received this info from Codership:
"The value of page_size parameter does not really matter,
it just regulates how often file creation/deletion operation happens.
but it makes little sense to have it bigger than the main cache size."
(which is very plausible to me).
I also was warned against removing gcache pages while the node is running.

Please:

  1. Get the config example and that chat advice in sync, they contradict each other.
  2. Check whether "size < page_size" may break the automatic cleanup.
  3. Document a way for manual cleanup, preferably without taking the node down.
@kirjaamo
Copy link
Collaborator

kirjaamo commented Feb 3, 2021

@byte Can we close this issue? Or should we document a way for manual cleanup, preferably without taking the node down?

@byte
Copy link
Contributor

byte commented Aug 21, 2024

@byte Can we close this issue? Or should we document a way for manual cleanup, preferably without taking the node down?

still incomplete

@kirjaamo
Copy link
Collaborator

@byte I checked that the System Configuration tutorial has:
wsrep_provider_options="gcache.size=300M; gcache.page_size=300M"

If manual cleanup instructions are needed, I don't know how manual cleanup is done. Do you know?

@byte
Copy link
Contributor

byte commented Aug 22, 2024

@byte I checked that the System Configuration tutorial has: wsrep_provider_options="gcache.size=300M; gcache.page_size=300M"

If manual cleanup instructions are needed, I don't know how manual cleanup is done. Do you know?

where is the current link as well

@kirjaamo
Copy link
Collaborator

@kirjaamo
Copy link
Collaborator

@byte Is there still something I must add to docs or can we close this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants