From 3400602ee668895c3c96fb5caf2336252a4803de Mon Sep 17 00:00:00 2001 From: Alexander Schwartz Date: Tue, 26 Nov 2024 09:16:15 +0100 Subject: [PATCH] Fix unordered list in caching guide (#35283) Closes #35006 Signed-off-by: Alexander Schwartz --- docs/guides/server/caching.adoc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/guides/server/caching.adoc b/docs/guides/server/caching.adoc index c541a0825c19..af667ff2f757 100644 --- a/docs/guides/server/caching.adoc +++ b/docs/guides/server/caching.adoc @@ -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 @@ -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: