-
Notifications
You must be signed in to change notification settings - Fork 101
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
Comments
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 Of course, that requires a bigger rewrite of the current WDYT? |
Sounds great! |
@mvhirsch Did you end up getting something working? |
I never finished my work and it's unlikely I'll do in foreseeable future. Feel free to take over @Sfonxs ! |
For now I have added a workaround to be able to continue my testing: $redis = Redis::fromExistingConnection(...);
$reflection = new ReflectionClass(Redis::class);
$property = $reflection->getProperty('prefix');
$property->setValue($redis, '{PROMETHEUS}_'); It's not a good solution since all the load will go to a single redis node (and it's using reflection), but at least it works... |
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:
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.
The text was updated successfully, but these errors were encountered: