8000 Fix unordered list in caching guide by ahus1 · Pull Request #35283 · keycloak/keycloak · GitHub
[go: up one dir, main page]
Skip to content

Fix unordered list in caching guide #35283

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stianst merged 1 commit into from
Nov 26, 2024
Merged

Fix unordered list in caching guide #35283

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/guides/server/caching.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,8 +97,8 @@ User and client sessions are automatically destroyed whenever the user performs

The session data are stored in the database by default and loaded on-demand to the following caches:

* sessions
* clientSessions
* `sessions`
* `clientSessions`

By relying on a distributable cache, cached user and client sessions are available to any node in the cluster so that users can be redirected
to any node without the need to load session data from the database. However, production-ready deployments should always consider session affinity and favor redirecting users
Expand All @@ -115,8 +115,9 @@ By default, user sessions are stored in the database and loaded on-demand to the
It is possible to configure {project_name} to store user sessions in the cache only and minimize the database utilization.

Since all the sessions in this setup are stored in-memory, there are two side effects related to this:
* Losing sessions on all Keycloak nodes restart
* Increased memory consumption

* Losing sessions on when all {project_name} nodes restart.
* Increased memory consumption.

Follow these steps to enable this setup:

Expand Down
0