The easiest approach is to set ip_nonlocal_bind to 1 and install keepalived on each node to handle the vip. Send all requests to this vip. Setting permissive mode is required. Apart from that I use the same settings as with normal Mysql
sql-mode="STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION,ERROR_FOR_DIVISION_BY_ZERO,NO_ZERO_DATE,NO_ZERO_IN_DATE,NO_ENGINE_SUBSTITUTION" innodb_rollback_on_timeout=1 innodb_lock_wait_timeout=600 max_connections=1000 and the "usual" modifications like innodb buffer pool. We are still in the implementation phase, so its limited tested. But so far, I didn’t have any issues. If you have multiple control planes, make sure to start only one initially. That one will provision the database schema. Cheers Juergen Am 17.09.24, 11:13 schrieb "Francisco Arencibia Quesada" <arencibia.franci...@gmail.com <mailto:arencibia.franci...@gmail.com>>: Good morning guys, I will go with mariadb, because percona +cloudstack is a nightmare. Thank you all Best regards On Mon, Sep 16, 2024 at 10:50 AM Rohit Yadav <rohit.ya...@shapeblue.com <mailto:rohit.ya...@shapeblue.com>> wrote: > 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 > <mailto:arencibia.franci...@gmail.com>> > Sent: Saturday, September 14, 2024 02:19 > To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> > <users@cloudstack.apache.org <mailto: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* > -- *Francisco Arencibia Quesada.* *DevOps Engineer*
