文章目录
- 一、Orchestrator简介
- 二、快速搭建Orchestrator环境
- 三、添加主从环境
- 四、修改集群别名
- 五、拖动界面修改主从关系
- 六、自动failover
一、Orchestrator简介
Orchestrator是一款开源,对MySQL复制提供高可用、拓扑的可视化管理工具,采用go语言编写,它能够主动发现当前拓扑结构和主从复制状态,支持MySQL主从复制拓扑关系的调整、支持MySQL主库故障自动切换(failover)、手动主从切换(switchover)等功能。
Orchestrator后台依赖于MySQL或者SQLite存储元数据,能够提供Web界面展示MySQL集群的拓扑关系及实例状态,通过Web界面可更改MySQL实例的部分配置信息,同时也提供命令行和api接口,以便更加灵活的自动化运维管理。Orchestrator 对MySQL主库的故障切换分为自动切换和手动切换。手动切换又分为recover、force-master-failover、force-master-takeover以及graceful-master-takeover。
相比于MHA,Orchestrator更加偏重于复制拓扑关系的管理,能够实现MySQL任一复制拓扑关系的调整,并在此基础上,实现MySQL高可用。另外,Orchestrator自身也可以部署多个节点,通过raft分布式一致性协议,保证自身的高可用。
Orchestrator主要有以下几个特征:
- 自动监测数据库复制的结构及其状态
- 提供了GUI,CLI,API等接口来检查复制拓扑的状态以及做一些调整的操作
- 支持自动的master failover,当复制结构的server挂掉以后(不管手动还是自动的),能够重新形成复制的拓扑结构
- 不依赖于特定的server版本或分支(MySQL, Percona Server, MariaDB or even MaxScale binlog servers)
- 支持多种类型的拓扑结构,不管是单个的主从还是成百上千个server组成的多级复制都不在话下
- 它的GUI不只是向你report拓扑状态,还可以在Orchestrator web页面通过拖拽或者删除节点来改变复制拓扑(CLI和API也能做)
Orchestrator的GitHub地址:
https://github.com/openark/orchestrator
https://github.com/outbrain/orchestrator/wiki/Orchestrator-Manual
https://github.com/github/orchestrator/tree/master/docs
Orchestrator的所有参数:
https://github.com/github/orchestrator/blob/master/go/config/config.go
官方建议的生产配置示例:
https://github.com/github/orchestrator/blob/master/docs/configuration-sample.md
二、快速搭建Orchestrator环境
-- 拉取小麦苗的镜像docker pull registry.cn-hangzhou.aliyuncs.com/lhrbest/lhrorchestrator:1.0-- 创建容器docker run -d --name lhrorchestrator -h lhrorchestrator \ -p 233:22 -p 3087:3389 -p 3000:3000 \ --privileged=true lhrbest/lhrorchestrator:1.0 \ /usr/sbin/init -- 进入容器 docker exec -it lhrorchestrator bash-- 启动后端存储MySQL库systemctl status mysqld MySQL用户名和密码:root/lhr-- 启动orchestratorsystemctl start orchestrator systemctl status orchestrator-- web访问:http://192.168.66.35:3000用户名和密码:lhr/lhr-- 日志:tailf /var/log/messages-- 参数文件/usr/local/orchestrator/orchestrator.conf.json
web界面如下所示:
三、添加主从环境
把配置好的复制实例加入到orchestrator,因为orch可以自动发现整个拓扑的所有实例,所以只需要添加任意一台实例即可。
这里,我有一套1主2从的环境,拓扑图如下所示:
[root@docker35 log]# mysqlrplshow --master=root:lhr@172.72.0.2:3306 --discover-slaves-login=root:lhr --verboseWARNING: Using a password on the command line interface can be insecure.# master on 172.72.0.2: ... connected.# Finding slaves for master: 172.72.0.2:3306# Replication Topology Graph172.72.0.2:3306 (MASTER) | +--- 172.72.0.3:3306 [IO: Yes, SQL: Yes] - (SLAVE) | +--- 172.72.0.4:3306 [IO: Yes, SQL: Yes] - (SLAVE)
下面开始把这套环境添加到orchestrator中:
添加成功。
我们再添加一套双主双从的环境:
选择任意一台MySQL服务器进行Discover操作,添加完成后,刷新页面如下:
四、修改集群别名
修改完成后,刷新页面:
注意:集群别名不支持中文。
五、拖动界面修改主从关系
手动修改主从关系:
六、自动failover
要实现自动failover,需要修改2个参数:
[root@lhrorchestrator orchestrator]# more orchestrator.conf.json | grep ClusterFilters "RecoverMasterClusterFilters": ["*"], "RecoverIntermediateMasterClusterFilters": ["*"],
这2个参数表示定义哪些集群可以自动failover和recover。
自动failover之前:
宕掉主库:
[root@lhrorchestrator /]# mysql -uroot -plhr -h172.72.0.2 -P3306mysql: [Warning] Using a password on the command line interface can be insecure.Welcome to the MySQL monitor. Commands end with ; or \g.Your MySQL connection id is 11357Server version: 5.7.30-log MySQL Community Server (GPL)Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.mysql> shutdown ;Query OK, 0 rows affected (0.00 sec)
刷新页面:
172.72.0.2自动被剔除,新主库变为172.72.0.3。
172.72.0.4指向了新的主库172.72.0.3。
172.72.0.2已宕机,边框为黑色:
接下来启动172.72.0.2,启动完成后:
需要我们手动加入集群:
[root@docker35 log]# mysql -uroot -plhr -h172.72.0.2 -P3306mysql: [Warning] Using a password on the command line interface can be insecure.Welcome to the MySQL monitor. Commands end with ; or \g.Your MySQL connection id is 13Server version: 5.7.30-log MySQL Community Server (GPL)Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.mysql> show slave hosts;Empty set (0.00 sec)mysql> show slave status;Empty set (0.00 sec)mysql> change master to-> master_host='172.72.0.3',-> master_port=3306,-> master_user='repl',-> master_password='lhr',-> master_auto_position=1;show slave status \G;Query OK, 0 rows affected, 1 warning (0.02 sec)mysql> mysql> start slave; Query OK, 0 rows affected (0.01 sec)mysql> show slave status \G;*************************** 1. row *************************** Slave_IO_State: Checking master version Master_Host: 172.72.0.3 Master_User: repl Master_Port: 3306Connect_Retry: 60 Master_Log_File: Read_Master_Log_Pos: 4 Relay_Log_File: master-relay-bin.000001Relay_Log_Pos: 4Relay_Master_Log_File: Slave_IO_Running: Yes Slave_SQL_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 0 Relay_Log_Space: 154 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: 0Master_SSL_Verify_Server_Cert: NoLast_IO_Errno: 0Last_IO_Error: Last_SQL_Errno: 0 Last_SQL_Error: Replicate_Ignore_Server_Ids: Master_Server_Id: 0 Master_UUID: Master_Info_File: mysql.slave_master_info SQL_Delay: 0 SQL_Remaining_Delay: NULL Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates Master_Retry_Count: 86400 Master_Bind: Last_IO_Error_Timestamp: Last_SQL_Error_Timestamp: Master_SSL_Crl: Master_SSL_Crlpath: Retrieved_Gtid_Set: Executed_Gtid_Set: bacfcde8-69dc-11eb-b240-0242ac480002:1-70574,bc6d26f0-69dc-11eb-bfa7-0242ac480003:1-5Auto_Position: 1 Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version: 1 row in set (0.00 sec)ERROR: No query specified mysql>
刷新页面:
可以看到,又回到了一主2从的环境。