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

scan_reader模式下,如何降低对源端的压力 #817

Open
xcjing opened this issue Jun 5, 2024 · 3 comments
Open

scan_reader模式下,如何降低对源端的压力 #817

xcjing opened this issue Jun 5, 2024 · 3 comments
Labels
type: question Further information is requested

Comments

@xcjing
Copy link

xcjing commented Jun 5, 2024

问题描述(Issue Description)

scan_reader模式中有个下面的参数,这个参数默认值是多少,能否通过这个参数控制对源端的压力?
#count = 1 # number of keys to scan per iteration

请在这里简要描述你遇到的问题。
如何避免Scan阶段对源库造成了过大压力,导致源系统吞吐和处理能力下降

Please provide a brief description of the issue you encountered.

环境信息(Environment)

  • RedisShake 版本(RedisShake Version):4.10
  • Redis 源端版本(Redis Source Version):7.0.7
  • Redis 目的端版本(Redis Destination Version):7.0.14
  • Redis 部署方式(standalone/cluster/sentinel):cluster
  • 是否在云服务商实例上部署(Deployed on Cloud Provider):yes

日志信息(Logs)

如果有错误日志或其他相关日志,请在这里提供。

If there are any error logs or other relevant logs, please provide them here.

其他信息(Additional Information)

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

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

@xcjing xcjing added the type: question Further information is requested label Jun 5, 2024
@xcjing
Copy link
Author

xcjing commented Jun 5, 2024

scan_reader模式下, 能否从slave节点同步,以降低对源端的压力

@xcjing
Copy link
Author

xcjing commented Jun 5, 2024

在scan_reader 下,虽然可以设置 perfer_replica=true, 但测试发现还是连接到master节点去同步,压力还是在master节点

@suxb201
Copy link
Member

suxb201 commented Jun 6, 2024

count = 1 改这个数字,小一些影响就很低。perfer_replica 目前还没支持。

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