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

RedisCluster support #153

Open
mvhirsch opened this issue Apr 23, 2024 · 2 comments
Open

RedisCluster support #153

mvhirsch opened this issue Apr 23, 2024 · 2 comments

Comments

@mvhirsch
Copy link

I'm currently working on RedisCluster support but do lack knowledge about keyspace and slots. Looks like there was once an approach (see #112), but at the time of writing there is no update.

I managed to connect my RedisCluster, but run into errors like this:

Warning: RedisCluster::eval(): All keys do not map to the same slot 

I read Redis Clustering best practices with keys but to be honest I'm clueless (or keyless? 😂 ). Any help is appreciated. I'd like to get this running soon, as one of my projects needs it.

@mvhirsch
Copy link
Author

I see there is also an open request for Redis Sentinel #95 and a pending PR for Predis #127.

I'd like to introduce a RedisAdapter that's capable to work with all of them, by abstracting and hiding away the special use-cases (like in RedisCluster or Predis). Using a method like the one symfony/cache uses, it would be easy to connect to any redis instance supported by them using a simple DSN.

https://github.com/symfony/symfony/blob/02c1e3c5c31dfc7f7f2b13515b060639cfac838a/src/Symfony/Component/Cache/Traits/RedisTrait.php#L87

Of course, that requires a bigger rewrite of the current Redis and I'm still not sure what role RedisNg is (see #152).

WDYT?

@LKaemmerling
Copy link
Member

Sounds great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants