Skip to content
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

error=[CROSSSLOT Keys in request don't hash to the same slot] #717

Closed
dba3306 opened this issue Dec 2, 2023 · 9 comments · Fixed by #786
Closed

error=[CROSSSLOT Keys in request don't hash to the same slot] #717

dba3306 opened this issue Dec 2, 2023 · 9 comments · Fixed by #786
Labels
type: bug Something isn't working type: question Further information is requested

Comments

@dba3306
Copy link

dba3306 commented Dec 2, 2023

问题描述(Issue Description)

实时同步,rdb阶段快结束的时候,报error=[CROSSSLOT Keys in request don't hash to the same slot]

环境信息(Environment)

  • RedisShake 版本(RedisShake Version):4.0.2
  • Redis 源端版本(Redis Source Version):7.0.9
  • Redis 目的端版本(Redis Destination Version):7.0.9
  • Redis 部署方式(standalone/cluster/sentinel):集群

日志信息(Logs)

2023-12-02 11:45:38 ERR [writer_10.1.x.x_6380] receive reply failed. cmd=[EXEC], error=[CROSSSLOT Keys in request don't hash to the same slot]

@dba3306 dba3306 added the type: question Further information is requested label Dec 2, 2023
@suxb201 suxb201 added the type: bug Something isn't working label Dec 8, 2023
@yasiping
Copy link

我也碰到了这个问题,主和备都是集群

@suxb201
Copy link
Member

suxb201 commented Mar 26, 2024

是的,这是 shake 的 bug,shake 需要过滤掉 multi 和 exec 命令才行。

@yasiping
Copy link

我也碰到了这个问题,主和备都是集群

问题找到了,是源和目标端的槽分配不一样,源端的每个节点的槽都是不连续的,都是几千个不连续的槽,目标端刚创建的集群都是平均连续分配的,这样源端多key操作,有可能多个key 是move到一台节点上,到源端就可能在不同节点上了。

@suxb201
Copy link
Member

suxb201 commented Mar 27, 2024

@yasiping 不影响,这是 shake 的 bug

@hanxinhisen
Copy link

@suxb201 请问有这个报错,如何干预一下呢

@suxb201
Copy link
Member

suxb201 commented Mar 27, 2024

@hanxinhisen
Copy link

@suxb201 这响应速度太快了,已完美解决问题。非常感谢。

@bennypea
Copy link

bennypea commented Jun 4, 2024

We are encountering this issue when trying to migrate a cluster to another cluster. Was this only fixed for stand alone instances? I am using v4.1.0

@suxb201
Copy link
Member

suxb201 commented Jun 4, 2024

@hanxinhisen The issue you're encountering might not be the same, please open a new issue with detailed description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working type: question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants