You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Version
kvrocks:2.5.1
redis-cli:4.0
Minimal reproduce step
The Redis manager tool can't recognize the Kvrocks when enabling the cluster mode. And I found is may be caused by missing redis_mode field in Kvrocks's info command.
Although we will already show cluster_enabled in INFO CLUSTER,
some tools such as redis manger will need this field to determine
whether it is cluster mode.
If cluster mode is enabled, redis_mode is displayed as cluster,
otherwise it is standalone.
Fixesapache#1926.
Although we will already show cluster_enabled in INFO CLUSTER,
some tools such as Redis Manager will need this field to determine
whether it is cluster mode.
If cluster mode is enabled, redis_mode is displayed as a cluster,
otherwise, it is standalone. We also use this opportunity to add
a kvrocks_mode field.
Fixes#1926.
Although we will already show cluster_enabled in INFO CLUSTER,
some tools such as Redis Manager will need this field to determine
whether it is cluster mode.
If cluster mode is enabled, redis_mode is displayed as a cluster,
otherwise, it is standalone. We also use this opportunity to add
a kvrocks_mode field.
Fixes#1926.
Search before asking
Version
kvrocks:2.5.1
redis-cli:4.0
Minimal reproduce step
The Redis manager tool can't recognize the Kvrocks when enabling the cluster mode. And I found is may be caused by missing
redis_mode
field in Kvrocks's info command.在使用开源工具redis manger时,发现无法识别kvrocks集群,排查日志,显示为redis mode返回值为kong
What did you expect to see?
Kvrocks's INFO command should return
redis_mode
to make the Redis manager happy.登录kvrocks执行INFO SERVER后,redis mode会返回对应信息。
What did you see instead?
登录kvrocks,执行INFO SERVER
没有返回该字段,而Redis会返回
Anything Else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: