YounguH
commented
2 months ago @ayurchen Hi, I think https://github.com/codership/galera/commit/fbf9167c4a0e03df0284f278024a9d41d3633c4e may fix this problem? But the refered bug was not found.
Open hy123f opened 3 months ago
YounguH
commented
2 months ago @ayurchen Hi, I think https://github.com/codership/galera/commit/fbf9167c4a0e03df0284f278024a9d41d3633c4e may fix this problem? But the refered bug was not found.
byte
commented
2 months ago hi @hy123f -- might you please contact us via email: info@codership.com or the contact form https://galeracluster.com/contact-us/
Mainly because we are interested in you doing this in MySQL 5.6 (which has been EOL for quite sometime now - we just moved 5.7 to that).
Looking forward to your email/contact form request.
Thank you
Hello, galera version is 3.34 and mysql version is 5.6.51.Two nodes. The gcache.page file is generated continuously and is not deleted. Eventually, the disk space is used up. In what scenario does this bug occur? Is there a stable reproduction scenario? How to solve this problem.
Analyze the collected host information. The last modification time of the galera.cache file is August 11. In addition, the memory resident set of the galera.cache file in the MySQL memory mapping information exported by using the pmap is inconsistent with the size of the mapping area. The galera.cache file is theoretically modified all the time that DDL happens. Today is August 25th. The problem has been happening for two weeks. The gcache.page file is still being generated.
galera.cache was last modified on August 11, 2024
The memory resident set of the galera.cache file is not the same size as the mapped region. Normally, the sizes should be the same.
In other environments, the galera version is 3.37 and the MySQL version is 5.7.38. No problem occurs.
Galera 3.34 and MySQL 5.6.51 are widely used on the live network. Can't replace it for now, eager to fix this issue.
Hi, if you see this bug, could you please reply as soon as possible? Thank you very much.