Issues with Redis Cluster about redbeat

[concreted]

According to https://redis.io/topics/cluster-spec,

Redis Cluster does not support multiple databases like the stand alone version of Redis. There is just database 0 and the SELECT command is not allowed.

so that explains why SELECT is not allowed in cluster mode happens.

@sibson Do you have any insight on the MOVED 8184 errors? Based on some info I found when Googling around it seems like whatever redis client is used has to know how to handle the redirect. I don't see anything about clustering in the pypi redis package docs though, it might not be able to handle this? I did find this package: https://github.com/Grokzen/redis-py-cluster

[sibson]

I've never tried using redis cluster. It looks like you are on the right track and a cluster aware client is required. I'm open to redbeat being made compatible with alternate redis client libraries.

[concreted]

Thanks, I'm planning to investigate adding a client that will allow cluster compatibility.

[sibson]

I believe this to be fixed by #64

[marvelph]

@sibson

Redis Cluster and Redis Sentonel are different solutions.
RedBeat now supports Redis Sentonel, but it does not seem to support Redis Cluster.
However, the HA configuration supported by Redis in AWS ElasticCache is Redis Cluster.
Please consider additional support for Redis Cluster.

[marvelph]

@sibson

I'm sorry.
I read the source code of RedBeat and found the corresponding code for Radis Cluster.
I guess it works if you specify redis-cluster as the schema in the URL and specify startup_nodes as an option.
The documentation doesn't mention it, so I misunderstood.