Dear Janis,
I use this setup myself in production. I'm pretty sure it works without
problem _as long as_ you write to a single node. On our side it is achieved
by way of HAProxy. I am not sure what kind of LB you use in Kubernetes so
caution may apply.
> By the way, is there any way to make sure
We are using a 3 nodes setup running in kubernetes.
Setup as described here:
https://mariadb.com/kb/en/installing-mariadb-kubernetes-with-the-operator/
Using the galera.yaml
As connection for the application we are using the hostname, as described here:
https://mariadb.com/kb/en/using-mariad
It should not be necessary to provide the PK id.
You just need to set wsrep_auto_increment_control to OFF. If you write to a
single node that's OK (you shouldn't write to multiple nodes with Galera
anyway)
-GL
Le mer. 1 mai 2019 à 13:50, Justin Swanhart a écrit :
> Since the PK values are hard
Since the PK values are hard coded in your application, provide the PK value in
the INSERT statement instead of using generated values.
> On May 1, 2019, at 4:11 AM, Guillaume Lefranc wrote:
>
> This feature is well known and documented:
>
> https://mariadb.org/auto-increments-in-galera/
>
>
This feature is well known and documented:
https://mariadb.org/auto-increments-in-galera/
Regards,
GL
Le mer. 1 mai 2019 à 08:46, Janis Heller a écrit :
> Hey community,
>
> I’m running Server version: 10.3.13-MariaDB-1:10.3.13+maria~bionic-log
> mariadb.org binary distribution of mariaDB (gal
what is result from this query :
show variables like '%increment%'
Pada Rabu, 1 Mei 2019 13.47.03 WIB, Janis Heller
menulis:
Hey community,
I’m running Server version: 10.3.13-MariaDB-1:10.3.13+maria~bionic-log
mariadb.org binary distribution of mariaDB (galera cluster).For local
de
6 matches
Mail list logo
