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

数据迁移阶段报错:ERR CROSSSLOT Keys in request don't hash to the same slot #913

Open
near-by opened this issue Dec 30, 2024 · 4 comments
Labels
type: question Further information is requested

Comments

@near-by
Copy link

near-by commented Dec 30, 2024

问题描述(Issue Description)

数据迁移阶段报错:ERR CROSSSLOT Keys in request don't hash to the same slot

环境信息(Environment)

  • RedisShake 版本(RedisShake Version):v4.2.2
  • Redis 源端版本(Redis Source Version):3.2.8
  • Redis 目的端版本(Redis Destination Version):3.2.8
  • Redis 部署方式(standalone/cluster/sentinel):源端单机部署,目的端集群部署
  • 是否在云服务商实例上部署(Deployed on Cloud Provider):否

日志信息(Logs)

image

其他信息(Additional Information)

请提供任何其他相关的信息,如配置文件、错误信息或截图等。

Please provide any additional information, such as configuration files, error messages, or screenshots.

@near-by near-by added the type: question Further information is requested label Dec 30, 2024
@suxb201
Copy link
Member

suxb201 commented Dec 30, 2024

你在源端调用 DEL 命令删除了多个 key,这些 key 不是属于同一个 slot 的。这种命令在集群上无法执行。

@near-by
Copy link
Author

near-by commented Dec 30, 2024

这个报错,是不是说明数据迁移已经进入到了增量同步的阶段了?
如果要保证正常迁移,是不是必须要在源端redis停掉批量操作多个key的程序?
还有没有其他解决方法?

@suxb201
Copy link
Member

suxb201 commented Dec 30, 2024

@near-by

  1. 对的,增量
  2. 停掉最简单,或者你写 lua 把这些命令过滤掉或者转成单一命令:https://tair-opensource.github.io/RedisShake/zh/filter/function.html#%E5%8F%98%E9%87%8F

@near-by
Copy link
Author

near-by commented Dec 30, 2024

@near-by

  1. 对的,增量
  2. 停掉最简单,或者你写 lua 把这些命令过滤掉或者转成单一命令:https://tair-opensource.github.io/RedisShake/zh/filter/function.html#%E5%8F%98%E9%87%8F

好的,谢谢!

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

No branches or pull requests

2 participants