Skip to content

Doc cautions about index repo with Redis Cluster #2904

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.

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

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,9 @@ 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: Using `RedisIndexedSessionRepository` with Redis Cluster is discouraged due to https://github.com/spring-projects/spring-data-redis/issues/1111[only being subscribed to events from one random redis node in the cluster],
causing a memory leak in the index and a slowdown in calls to `findByPrincipalName`. Using `RedisIndexedSessionRepository` in tandem with a redis that does not have multiple shards avoids this problem.

=== Configuring the `RedisSessionRepository`

==== Using Spring Boot Properties
Expand Down