Hi Francisco, Active-active DB cluster setup isn't supported or possible due to the GET_LOCK/RELEASE_LOCK limitations you've found. However, if you're using a MySQL router or ProxySQL or similar middleware, then you can split reads across nodes but write to only a single node at a time.
Alternatively, you can use Active-Backup setup, such that you allow ACS mgmt servers to write (&read) from a single node but switch in case it goes down. Many users actually use an primary-backup DB deployment model with frequent/hourly DB backups. Regards. ________________________________ From: Francisco Arencibia Quesada <arencibia.franci...@gmail.com> Sent: Saturday, September 14, 2024 02:19 To: users@cloudstack.apache.org <users@cloudstack.apache.org> Subject: CloudStack Compatibility with Percona XtraDB Hello Guys, I am currently using Percona XtraDB Cluster for my database, but CloudStack relies on functions like GET_LOCK and RELEASE_LOCK, which are not recommended in a Galera-based cluster. Setting pxc_strict_mode = PERMISSIVE allows CloudStack to function, but this causes issues with replication consistency and stability. If I set pxc_strict_mode = ENFORCING, CloudStack stops working because it uses these functions, but setting it to PERMISSIVE breaks the replication in the cluster. Is there any way to configure Percona XtraDB Cluster to allow CloudStack to work properly without compromising the integrity of the replication? I use CS 4.18, 4.19 both with the same problem. Thanks a lot in advance :) -- *Francisco Arencibia Quesada.* *DevOps Engineer*
