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
你是否希望来认领这个优化建议。
「 Y / N 」
在对接3.5.1的Kraft模式的kafka集群时,可以将controller显示改为leader,因为有很多controller每分钟都切换显示对数据库造成不必要的存储,可以显示leader来更好的判断集群状态
The text was updated successfully, but these errors were encountered:
你是不是采用combined node模式?这种部署的模式不是生产的模式,生产模式需要把broker和controller分开部署,比如3 broker + 3 controller,know streaming似乎取不到controller的数量,集群一直是不健康状态
比如我的节点ID:1、2、3是controller,4、5、6是broker,系统只能看到4、5、6,且错认为4,5,6其中之一是controller
此外系统获取我的controller的数量等于0,这就不对了,明明有1个controller(1、2、3中的一个),而combined node模式下可以获取,因为节点既是broker也是controller
Sorry, something went wrong.
我建议在kraft模式下,集群设置上增加controller节点的连接框,并增加对controller节点的信息展示,并且集群健康检测规则上,能够检测到broker和controller分开部署时的controller节点
kraft模式下,kafka metadata APIs 返回的是随机controller ID,导致 ks_km_kafka_controller 数据量不断地快速增长,该表也有必要 添加一个cluster_phy_id字段的索引。
No branches or pull requests
你是否希望来认领这个优化建议。
「 Y / N 」
环境信息
需要优化的功能点
在对接3.5.1的Kraft模式的kafka集群时,可以将controller显示改为leader,因为有很多controller每分钟都切换显示对数据库造成不必要的存储,可以显示leader来更好的判断集群状态
建议如何优化
The text was updated successfully, but these errors were encountered: