Repository navigation
Replies: 2 comments 3 replies
|
@RomekCDPR Regarding your comment "Eviction/expiration in embedded cache leads to Failed to replace entity warnings + high latency." . There is a discussion may be related to this at #16405 . Came across your question while I am trying to find the root cause. It would be great if you can provide some details why using embedded cache leads to "Failed to replace entity" warning. |
|
Since this question was asked, several changes happend to Keycloak. The setup asked for in the question is now supported since Keycloak 26.0 which was released in October 2024: Since that release Keycloak by default stores all sessions in the database. You are no longer limited by memory usage. Depending on the logins per second and token refreshes per second, you might be limited by DB IO. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
My team is planning to implement solution based on the Keycloak. I'd like to ask the community for a feedback regarding possible setups.
Requirements
Alternatives
Diagrams represent only 1 node for readability.
Embedded Infinispan with JDBC persistence
Pros:
Cons:
Embedded Infinispan with eviction and JDBC persistence
Pros:
Cons:
Failed to replace entity warnings+ high latency.Embedded Infinispan + offline sessions
Pros:
Cons:
Embedded Infinispan with eviction/expiration + offline sessions
Can be more feasible with #24274.
Pros:
Cons:
Failed to replace entity warnings+ high latency.Embedded Infinispan + cross-site replication
Cons:
Embedded Infinispan with eviction/expiration + remote Infinispan with JDBC persistence
Pros:
Cons:
Failed to replace entity warnings+ high latency.Embedded Infinispan with eviction + remote Infinispan with eviction/expiration + offline sessions
Pros:
Cons:
Failed to replace entity warnings+ high latency.Embedded Infinispan with eviction + remote Infinispan + cross-site replication
Pros:
Cons:
Failed to replace entity warnings+ high latency.Custom
UserSessionProviderCustom DB persistence with optional in-memory cache optimisations.
Pros:
Cons:
UserSessionProviderandUserSessionModel.Outcome
We are leaning towards "Custom
UserSessionProvider" - the only alternative that meets all of the requirements - even with hight implementation/maintenance costs.All reactions