m 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.
> >
> >
> >
> >
> > ________
> &g
_
> From: Francisco Arencibia Quesada <mailto:arencibia.franci...@gmail.com>>
> Sent: Saturday, September 14, 2024 02:19
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org>
> mailto:users@cloudstack.apache.org>>
> Subject: CloudStack Compatibili
cisco Arencibia Quesada
> Sent: Saturday, September 14, 2024 02:19
> To: 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 GE
Could you share your config file Juergen?
I have a keepalive but in the haproxies.
Kind regards
On Mon, Sep 16, 2024 at 3:03 PM Jürgen Gotteswinter
wrote:
> Hello,
>
> i am currently also working on such a setup, like you said it causes
> issues when distributing the write requests. My solution
Hello,
i am currently also working on such a setup, like you said it causes issues
when distributing the write requests. My solution is to use keepalived on each
cluster node to make sure writes only go to a single node (VIP with NAT 3306 ->
127.0.0.1:3306).
So far, no problems.
Cheers,
Jue
__
From: Francisco Arencibia Quesada
Sent: Saturday, September 14, 2024 02:19
To: 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_LO
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 replicati
