在集群更新期间，可以通过积极关闭领导者来减少超时（10s？）？
如果AeronCluster在运行时想更新领导者节点，则群集将面临不可用的心跳超时（10s？）。是否可以向集群工具添加信号以使领导者节点退位并让其他追随者积极开始选举？ （我尝试了remove-ember，但该节点以后无法加入群集。
If AeronCluster wants to update the leader node when running, the cluster will face the heartbeat timeout (10s?) unavailability. Is it possible to add a signal to ClusterTools to make the leader node abdicate and let other followers actively start the election? (I tried remove-member, but the node cannot join the cluster later.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
通过将媒体驱动程序与每个节点上的共有模块分开，这是可能的。为了减少领导者的10次超时，可以关闭领导者的共识模块，同时让媒体驾驶员登上领导者。然后，追随者将检测到日志通道已关闭并立即参加新的选举。
This is possible by running the media driver separate from the consensus module on each node. To reduce the 10s timeout on the leader the consensus module on the leader can be closed while leaving the media driver on the leader running. The followers will then detect the log channel has closed and immediately enter a new election.