-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Keyspace Events in Redis Cluster get lost [DATAREDIS-534] #1111
Comments
I'm seeing this same issue as reported with spring-projects/spring-session#2230. In my use case, it negatively affects Spring Authorization Server when using SpringSessionBackedSessionRegistry with a sharded redis where the authorization server's token endpoint ends up reading every session including the expired ones in the principal index. The expired sessions stack up which linearly increases the token endpoint latency. |
Due to spring-projects#1111, applications can suffer from missing important Keyspace events. This adds a caution to the docs to help others avoid running into this problem.
Due to spring-projects#1111, applications can suffer from missing important Keyspace events as described at spring-projects/spring-session#2230. This adds a caution to the docs to help others avoid running into this problem.
Due to spring-projects#1111, applications can suffer from missing important Keyspace events as described at spring-projects/spring-session#2230. This adds a caution to the docs to help others avoid running into this problem.
Due to spring-projects#1111, applications can suffer from missing important Keyspace events as described at spring-projects/spring-session#2230. This adds a caution to the docs to help others avoid running into this problem.
Due to spring-projects#1111, applications can suffer from missing important Keyspace events as described at spring-projects/spring-session#2230. This adds a caution to the docs to help others avoid running into this problem.
Applications can suffer from missing important Keyspace events as described at spring-projects/spring-session#2230. This adds a caution to the docs to help others avoid running into this problem. Related ticket spring-projects#1111
Due to spring-projects/spring-data-redis#1111, applications can suffer from missing important Keyspace events as described at #2230. This adds a caution to the docs to help others avoid running into this problem and suggests an alternative. Mitigates #2230.
Any update on this issue? This is a blocker for us. We used Redis Repository pattern with search capabilities without knowing about this issue. |
Mark Paluch opened DATAREDIS-534 and commented
Keyspace notifications in Redis Cluster are published only to the local node (see redis/redis#2541. Keyspace notifications are not broadcasted to all nodes).
Spring Data Redis subscribes only to one (random) node and so the expiry event may be received but that depends on which node the subscription resides and on which cluster node a key expired.
The recommended workaround is to:
Affects: 1.7.2 (Hopper SR2)
Issue Links:
("is duplicated by")
("is duplicated by")
2 votes, 3 watchers
The text was updated successfully, but these errors were encountered: