We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
比如: 场景1: 一主多从 M(master), S0(slaveOfM),S1(slaveOfM) 当M挂了,S0升级为master M0,老的M几分钟后恢复,恢复后如果M作为M0的slave,这时候数据是全量同步还是增量的?
场景2: 链式主从 master M, S0(slaveOfA),S1(slaveOfS0), 当S0挂了,S1挂到M作slave,是否增量同步呢?
The text was updated successfully, but these errors were encountered:
对于场景1,M作为M0的slave的话,是无法增量的,因为M0之前没有为M记录指令的序号SEQ。 对于场景2,S1挂到M,也是无法增量的。 因为一次建立主从的过程,是从库获取主库snapshot,以及记录了建立那一刻主库的SEQ,有SEQ通过SEQ来到主库取实现增量同步。上述场景1的M和场景2的S1都没有正确的snapshot+seq。 PS:GoRedis目前还在beta阶段,内部使用的,还会有一些小问题存在,等各种场景的维护文档出来后使用会方便些。
Sorry, something went wrong.
No branches or pull requests
比如:
场景1:
一主多从
M(master), S0(slaveOfM),S1(slaveOfM)
当M挂了,S0升级为master M0,老的M几分钟后恢复,恢复后如果M作为M0的slave,这时候数据是全量同步还是增量的?
场景2:
链式主从
master M, S0(slaveOfA),S1(slaveOfS0), 当S0挂了,S1挂到M作slave,是否增量同步呢?
The text was updated successfully, but these errors were encountered: