You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried setting up proxysql in between some java applications (e.g. Keycloak Cluster) and a three node galera cluster. My setup is to install proxysql on each application server, the application is connected to the local proxysql application. The local proxysql then is connected to a galera cluster.
So my setup is:
Host-1
Host-2
Host-3
Keycloak
Keycloak
Keycloak
Proxysql
Proxysql
Proxysql
Apache
Apache
Apache
keepalive + haproxy
keepalive + haproxy
keepalive + haproxy
Talking to Host-4;Host-5 and Host-6 running a galera clusting via a TLS encrypted database connection.
All of my Hosts run Ubuntu Server 20.04 with the latest patches.
My Issue is when updating the version of one of my java apps, flyway makes some db-migrations for the new version but there seems to go something horribly wrong as the keycloak log give me an error: ````Error: 1305-42000: PROCEDURE keycloak_db_1.current_schema does not exist`````. When running the very same update without proxysql in between, the flyway migration work just fine.
Hello everyone,
I tried setting up proxysql in between some java applications (e.g. Keycloak Cluster) and a three node galera cluster. My setup is to install proxysql on each application server, the application is connected to the local proxysql application. The local proxysql then is connected to a galera cluster.
So my setup is:
Talking to Host-4;Host-5 and Host-6 running a galera clusting via a TLS encrypted database connection.
All of my Hosts run Ubuntu Server 20.04 with the latest patches.
My Issue is when updating the version of one of my java apps, flyway makes some db-migrations for the new version but there seems to go something horribly wrong as the keycloak log give me an error: ````Error: 1305-42000: PROCEDURE keycloak_db_1.current_schema does not exist`````. When running the very same update without proxysql in between, the flyway migration work just fine.
The proxysql looks as follows:
The Proxysql Log is not very much helping:
Thanks in advance
The text was updated successfully, but these errors were encountered: