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
通过#9184看到了同样问题,我在平滑升级1.3.2->2.0.3时也遇到了 1、当三个节点都升级到2.0.3此时会不停的打印日志:upgrade check result false,但是一旦有一个节点readyToUpgrad=ture时,就会导致集群算法不一致,然后就报错:receive invalid redirect request from peer。 2、升级文档里面说到的: ---当集群升级完成后,可以先观察一段时间运行情况,当确认无误后,可以关闭双写,从而释放性能--- 这里关闭双写是否能在所有节点readyToUpgrad=false的时候就关闭?如果不能那不就根本没法解决这个问题,毕竟问题是发生在readyToUpgrad状态变更的过程中的。
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
1、强制关闭,会影响300多个在存的注册服务之间的通信么? 2、很有可能是所说的情况,毕竟300多个服务是实时在线的,我也只敢平滑升级
No branches or pull requests
通过#9184看到了同样问题,我在平滑升级1.3.2->2.0.3时也遇到了
1、当三个节点都升级到2.0.3此时会不停的打印日志:upgrade check result false,但是一旦有一个节点readyToUpgrad=ture时,就会导致集群算法不一致,然后就报错:receive invalid redirect request from peer。
2、升级文档里面说到的:
---当集群升级完成后,可以先观察一段时间运行情况,当确认无误后,可以关闭双写,从而释放性能---
这里关闭双写是否能在所有节点readyToUpgrad=false的时候就关闭?如果不能那不就根本没法解决这个问题,毕竟问题是发生在readyToUpgrad状态变更的过程中的。
The text was updated successfully, but these errors were encountered: