support for redis 3.2? about corvus HOT 9 CLOSED

Is this just about newly introduced commands in 3.2?
The Cluster API should be fairly stable between 3.0 and 3.2 (I didn't check whether the output of CLUSTER NODES changed, I will do so tomorrow)

from corvus.

CLUSTER NODES is the same in 3.0 and 3.2 so corvus should be able to work with Redis 3.2 without problems

from corvus.

Redis 3.2 provides some good features and supporting them may be just adding some new items to command table. But actually there is no 3.2 in our production environment and I think supporting 3.2 needs further tests. We are trying new redis version in progress but we will not support it very soon.

from corvus.

Yes, it's all about the new commands.
As long as the CLUSTER NODES, ASK(ING), MOVED are not changed, corvus should be able to work with redis 3.2.

from corvus.

So CLUSTER NODES is the same in 3.0 and 3.2, but it changed in unstable (it appends @<busport>.
In order to be forwards-compatible corvus could already add a check for that or switch to the more stable CLUSTER SLOTS API instead.

from corvus.

In fact we used CLUSTER SLOTS before #64 . The problem is after the large clusters scale up and down for several times, the slot ranges will be broken into small pieces and the response of CLUSTER SLOTS can be large and cause performance problem.

from corvus.

Can I assume that corvus v0.2.7 supports Redis 3.2? The release notes mention that Redis 4 is supported. Just wondering why this issue is still open? Thanks.

from corvus.

@joshweir corvus v0.2.7 is just compatible with Redis 3.2 and 4, but still doesn't support new commands of them.
Sorry for the misleading release notes. I will update it.

from corvus.

@doyoubi It's no problem. Thanks for the clarification.

from corvus.