WIP: fix_synced_failed #2045
Closed
WIP: fix_synced_failed #2045
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
背景
当前在 K8s 环境下自动化部署 Pika 集群的时候会出现 Synced_failed 的问题，但是测试后发现其实主从节点双方数据同步本身是没有问题的，只是在 Dashboard 页面上显示出现了问题，原本情况是所有节点都会出现 Synced_failed，本 PR 改到只有从节点出现 Synced_failed，当然这不是最终的解决办法。
想法
目前在 K8s 环境中进行自动化部署 Group 和往里面添加 Pika 并建立主从关系是通过一个脚本文件
admin.sh来实现的，只是这里有个问题是在一个 Group 中建立主从关系使用的是 codis-admin 命令中的codis-admin [-v] --dashboard=ADDR --sync-action --create --addr=${KB_POD_FQDN}:9221调用完这个命令后会出现 Synced_failed 的情况，如果注释掉这行则主从不会进行绑定同时也没有 Synced_failed 的情况。想问下大家如果不用 codis-admin 命令的绑定主从的话还有其他的方法的吗？或者 Synced_failed 的问题怎么去排查，目前通过双击那个绿色的小扳手可以使 Synced_failed 消息移除修改前:
修改后:
讨论
大家有好的想法欢迎在评论区留言
fix: #1967