Doc cautions about index repo with Redis Cluster
Due to https://github.com/spring-projects/spring-data-redis/issues/1111, applications can suffer from missing important Keyspace events as described at https://github.com/spring-projects/spring-session/issues/2230. This adds a caution to the docs to help others avoid running into this problem and suggests an alternative. Mitigates #2230.
This commit is contained in:
committed by
Marcus Hert Da Coregio
parent
0db644b620
commit
8b485b6020
@@ -122,6 +122,8 @@ For example, it may create indexes based on session attributes like user ID or l
|
||||
These indexes allow for efficient querying of sessions based on specific criteria, enhancing performance and enabling advanced session management features.
|
||||
In addition to that, `RedisIndexedSessionRepository` also supports session expiration and deletion.
|
||||
|
||||
CAUTION: When using `RedisIndexedSessionRepository` with Redis Cluster you must be aware that https://github.com/spring-projects/spring-data-redis/issues/1111[it only subscribe to events from one random redis node in the cluster], which can cause some session indexes not being cleaned up if the event happened in a different node.
|
||||
|
||||
=== Configuring the `RedisSessionRepository`
|
||||
|
||||
==== Using Spring Boot Properties
|
||||
|
||||
Reference in New Issue
Block a user