-
Feature Request
-
Resolution: Done
-
Major
-
None
-
2.5 ER1
-
0
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
3scale 2019-03-25, 3scale 2019-04-08
We need to make possible for customers to use 3scale on-prem with Redis Enterprise.
One known implication of this is that it needs to be possible to configure components to establish connections to single instance/single db Redis.
Note (from email with dortiz-1):
Redis cluster is a way provided by Redis to shard data across multiple Redis instances. This was introduced in Redis 4.0. In order to use this, you need a client that supports Redis cluster. In the case of the 3scale backend, we use an old version of the client that does not support redis cluster. I don't know whether the system component supports this or not.
I think confusion is caused because Redis enterprise also offers a way to shard data across multiple Redis instances. However, it does not require a client that supports Redis cluster. The reason is that instead of configuring all the instances in "cluster mode", Redis Enterprise uses an intermediate proxy that's responsible for the sharding.
- relates to
-
THREESCALE-2229 Document migration procedure to Redis Enterprise
- Closed
1.
|
Prevent system from directly switching redis logical dbs | Closed | Unassigned | ||
2.
|
Namespace redis keys per connection client | Closed | Unassigned | ||
3.
|
Deployment steps for Redis Enterprise as system-redis | Closed | Unassigned | ||
4.
|
Fix deployment steps for Redis Enterprise with HA templates | Closed | Unassigned |