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

rump模式下源端支持cluster #149

Closed
vinllen opened this issue Aug 16, 2019 · 3 comments
Closed

rump模式下源端支持cluster #149

vinllen opened this issue Aug 16, 2019 · 3 comments
Assignees

Comments

@vinllen
Copy link
Contributor

vinllen commented Aug 16, 2019

目前rump模式下源端如果是cluster是有问题的,考虑支持
image

@vinllen vinllen added enhancement and removed bug labels Aug 16, 2019
@vinllen
Copy link
Contributor Author

vinllen commented Aug 17, 2019

这个可能是用户源端发生了Move slot操作,或者节点配置不对,理论上不应该由这个报错。

@vinllen
Copy link
Contributor Author

vinllen commented Nov 8, 2019

用户源端是6个节点(3主3从),但是source.address配置了所有6个节点,是会报这个错误。
后面加上校验,防止用户配置出错。
报错的原因是,slave本身不接受读命令,默认redirect到master上,除非配置了readonly(命令行配置的readonly只是当前连接生效的)。
1.8版本起,cluster的角色只能是master,不能为slave。
image

vinllen added a commit that referenced this issue May 2, 2020
* add CI

* in debug CI

* in debug CI

* in debug CI

* in debugging CI

* in debug CI

* in debugging CI

* in debug CI 2

* split sync code from sync.go to dbSync directory to make code clean

* finish adjust sync mode code

* update a lit

* add cluster node list judge, only accpet role master. see #149

* update ChangeLog

* update ChangeLOG 2

* add CI

* in debug CI

* in debug CI

* in debug CI

* in debugging CI

* in debug CI

* in debugging CI

* in debug CI 2

* split sync code from sync.go to dbSync directory to make code clean

* finish adjust sync mode code

* update a lit

* add cluster node list judge, only accpet role master. see #149

* update ChangeLog

* update ChangeLOG 2

* merge commit in feature-1.6 manually. see pull/201

* resuming from break-point, in coding

* add resume_from_break_point in configuration

* resuming from break-point, in coding 2

* resuming from break-point, finish offset adjust

* merge v1.6.24 manully

* update some metrics

* update, add run-id

* almost finish resume from break-point

* polish resume from breakpoint

* release 1.7-unstable v1

* modify ChangeLog

* restore add parameters judge when version >= 5.0

* cherry pick 3ea30b0

* update redis-go-cluster to add more log details

* cherry pick 0e10b0d

* bugfix of sendId, see #222

* improve: rename used -> available in delayChan. see #233

* block password, see #229

* set auth_type to 'auth' as default, see #237

* release v1.6.26

* modify ChangeLog

* polish conf comment

* merge 16.27 manually

* 1. polish conf 2. add filter key for redis-shake-checkpoint

* 1. polish conf 2. add filter key for redis-shake-checkpoint2

* unify offset by only one, step 1: modify checkpoint and add ut

* unify offset by only one, step 2: modify syncIncrease.go. haven't test yet

* unify offset by only one, step 3: finish test

* finish cluster resuming from break point and pass simple test

* update driver

* add picture of resuming from break point

* add picture of resuming from break point

* add checkpoint and conf version

* cherry pick 1d6c8ed from v1.6.28

* modify the checkpoint fcv

* release v2.0

* merge v1.6.28

* update redis-go-cluster to remove SELECT judge, see #273

* disable target.db when enable resume_from_break_point

* release v2.0.1
@suxb201
Copy link
Member

suxb201 commented Aug 18, 2021

todo:文档需要介绍具体些

@suxb201 suxb201 self-assigned this Aug 18, 2021
@suxb201 suxb201 pinned this issue Aug 18, 2021
@suxb201 suxb201 unpinned this issue Sep 6, 2021
@suxb201 suxb201 closed this as completed Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants