Re: [keycloak-user] Galera Replication and Caching
Which Keycloak version are you using? If it's older than 1.9.8.Final,
then it's suggested to upgrade as there were caching fixes meanwhile.
There is also possibility to disable caching in keycloak-server.json (or
in standalone.xml in latest version). It's mentioned in the docs how to
do it.
Finally it may also help if you have opportunity to try with 2 Keycloak
cluster nodes configured against same DB node. This may help to better
isolate the problem and see if it's related to caching or to MariaDB
cluster.
Marek
On 10/10/16 22:31, Josh Cain wrote:
Hi all,
We're running into a problem with a couple of MariaDB instances +
Galera. When I go to add a client on the first Keycloak node/DB (we'll
call it DB01), it add successfully. I can then go to the second
Keycloak Node/DB (call this one DB02) and do not see the client on the
'clients' list. However, if I were to add the same client on DB02, I
get the expected 'client with ID already exists' message. What's more,
if I bounce the Keycloak node that talks to DB02, the client list
populates with the new entry added at DB01.
Was guessing it's some kind of caching issue - is there a setting where
I can alter this behavior?