Repository navigation
Replies: 2 comments
|
Running KC without any cache is going to be tricky. Keycloak relies heavily on Infinispan for more than just sessions — it also caches realms, clients, users, authorization policies, etc. Going fully DB-only means every single request hits the database for all of that, which can be pretty rough on performance. That said, if your nodes really can't talk to each other, your best bet is probably using an external Infinispan cluster that both nodes connect to remotely. You'd configure it with the If even that's not an option and you truly want DB-only, you'd need to look at What's the constraint that prevents the nodes from seeing each other? If it's just a network segmentation thing, sometimes opening a single port for JGroups (default 7800) is easier than fighting the cache architecture. |
|
There is a technical spike that is now turning into an enhancement in #49469. This might land as an experimental feature in 26.7.0 and would allow for a setup you ask for.
I would like to understand more why this is the case for you. In the issue above, each cluster is then polling the database every 100ms for invalidations for any changes realm data. So updating a client or a group then takes 50-100 ms to complete. Please join that other issue to discuss if this scenario would be ok for you, or rather not. |
Uh oh!
There was an error while loading. Please reload this page.
I'm trying to run a Keycloak 26.6.1 setup with two nodes, but without using any cache (neither embedded nor external). The goal is to have both nodes fully synchronized exclusively through the database.
In my scenario, the Keycloak nodes cannot communicate with each other directly. Because of this, I would prefer to rely entirely on the database for synchronization, avoiding the need for clustering or an external Infinispan cache, in order to simplify the architecture.
From what I understand in the documentation and this blog post, it seems that such a setup is not supported, but I would like to confirm:
Thanks in advance!
All reactions