使用keepalived+orchestrator+mysql架构时,不要将orchestrator的依赖库放置到集群的mysql上面
举个栗子:当主库宕机之后,keepalived的VIP直接释放,如果orchestrator通过VIP访问数据库就不通,此时orchestrator会直接全部停机,从而无法保证自动切换
较为详细的安装配置过程可以参考:https://riverdba.github.io/2019/03/19/orchestrator/
有几个问题补充一下:
1、修改配置:
/etc/orchestrator.conf.json
"RecoverMasterClusterFilters": [
"*"
],
2、orchestrator高可用配置raft:详见raft配置
"RaftEnabled": true,
"RaftDataDir": "/var/lib/orchestrator",
"RaftBind": "10.0.0.2",
"DefaultRaftPort": 10008,
"RaftNodes": [
"10.0.0.1",
"10.0.0.2",
"10.0.0.3"
],