Skip to content
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

SSubscribe support required for Redis sharded pub sub #3065

Closed
gaurav-garg-jg opened this issue Dec 3, 2024 · 1 comment
Closed

SSubscribe support required for Redis sharded pub sub #3065

gaurav-garg-jg opened this issue Dec 3, 2024 · 1 comment
Labels
status: duplicate A duplicate of another issue

Comments

@gaurav-garg-jg
Copy link

Description: The Pub/Sub mechanism needs to handle subscriptions across multiple shards. We are requesting support for SSubscribe, which would allow efficient and reliable subscribing to channels across Redis shards. This feature would ensure that messages are properly delivered across different Redis instances in a sharded setup, facilitating seamless communication across distributed systems.

Use Case: In scenarios where Redis is sharded for scalability or partitioning, subscribing to channels across shards becomes a challenge. The ability to use SSubscribe in such environments would simplify message distribution and consumption, improving performance and reliability for large-scale applications relying on Redis Pub/Sub for real-time messaging.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Dec 3, 2024
@mp911de mp911de added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged labels Dec 3, 2024
@mp911de
Copy link
Member

mp911de commented Dec 3, 2024

This is a duplicate of #3019.

@mp911de mp911de closed this as not planned Won't fix, can't repro, duplicate, stale Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants