1

When trying to add a new node to a MySQL Innodb cluster using Cluster.addInstance() and selecting the Clone option, within 2 or 3 minutes the donor nodes memory usages hits 100% on a server with 36Gb of memory. At 100% memory usage the server becomes unresponsive and the recipient server moves to another server in the cluster, tries to clone, and the memory usage of the 2nd donor hits 100%. The entire cluster is degraded in under 10 min and unavailable.

This is on a Production server so the consequences here are pretty devastating.

I'm running MySQL 8.0.35-27 on Debian 12 Bookworm.

I have not encountered this problem setting up a test cluster with a small amount of data, which I have done several times to ensure I'm doing everything correctly. However on my Production server with about 125Gb of data, this problem occurs consistently.

Has anyone else experienced this problem or know what the cause might be?

Thank you.

Improve this question
1
  • What is your HOSTING company? Additional DB information request FROM each server - donor and recipient, please. OS, Version? RAM size, # cores, any SSD or NVME devices on MySQL Host server? Post TEXT data on justpaste.it and share the links. From your SSH login root, Text results of: A) SELECT COUNT(*) FROM information_schema.tables; B) SHOW GLOBAL STATUS; after minimum 24 hours UPTIME - if possible C) SHOW GLOBAL VARIABLES; D) SHOW FULL PROCESSLIST; E) STATUS; not SHOW STATUS, just STATUS; for server workload tuning analysis to provide suggestions.
    – Wilson Hauck
    Commented Apr 9 at 18:55

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .