Shulou(Shulou.com)05/31 Report--

This article will explain in detail about the MySQL high availability tool Orchestrator how to install raft multi-node mode, the content of the article is of high quality, so the editor will share it for you to do a reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Surroundings

Orchestrator machines: 10.10.30.150,10.10.30.128, 10.10.30.145orchestrator back-end Metabase MySQL:10.10.30.150, 10.10.30.128,10.10.30.145 Target Monitoring Database: 10.10.30.130 orchestrator 3306 install orchestrator Metabase MySQL install MySQL on each orchestrator machine, omitting the installation steps, the same as the regular installation of MySQL. The libraries and users needed to create orchestrator after the installation is complete. CREATE USER 'orchestrator'@'127.0.0.1' IDENTIFIED BY' orchestrator';GRANT ALL PRIVILEGES ON `orchestrator. * TO 'orchestrator'@'127.0.0.1'

Here, the meta-database MySQL and orchestrator are on the same machine, so '127.0.0.1' is used when creating an account. If it is not on the same machine, change IP to ip, the machine where orchestrator resides.

Password is modified as needed

Install orchestrator download the orchestrator installation package, here using orchestrator-3.1.2-linux-amd64.tar.gz https://github.com/github/orchestrator/releases on each orchestrator machine, extract the orchestrator installation package. Tar-xvzf orchestrator-3.1.2-linux-amd64.tar.gz-C / move / usr/local/orchestrator/orchestrator-sample.conf.json to / etc And named orchestrator.conf.json [root@10-10-30-150 orchestrator] # lsorchestrator orchestrator-sample-sqlite.conf.json orchestrator-sample.conf.json resources [root@10-10-30-150 orchestrator] # cp orchestrator-sample.conf.json / etc/orchestrator.conf.json target monitoring database authorization is authorized on the target database to be monitored. The target database here is: 10.10.30.130:3306CREATE USER 'orchestrator'@'orch_host' IDENTIFIED BY' orch_topology_password'

GRANT SUPER, PROCESS, REPLICATION SLAVE, RELOAD ON *. * TO 'orchestrator'@'orch_host'

GRANT SELECT ON mysql.slave_master_info TO 'orchestrator'@'orch_host'

GRANT SELECT ON ndbinfo.processes TO 'orchestrator'@'orch_host';-Only for NDB Cluster, change the' orch_host' to the ip,'orch_topology_password' of the server where the orch resides and change the appropriate password. Here orch_host is 10.10.30%, change the password to orchestrator. Modify orchestrator configuration file modify / etc/orchestrator.conf.json as follows: / / configure orchestrator backend Metabase information. "MySQLOrchestratorHost": "127.0.0.1", "MySQLOrchestratorPort": 3306, "MySQLOrchestratorDatabase": "orchestrator", "MySQLOrchestratorUser": "orchestrator", "MySQLOrchestratorPassword": "orchestrator",. / / configure orchestrator monitoring target database information "MySQLTopologyUser": "orchestrator", "MySQLTopologyPassword": "orchestrator" . / / configure the relevant parameters of raft "RaftEnabled": true, "RaftDataDir": "/ var/lib/orchestrator", "RaftBind": "10.10.30.150", # Native ip or hostname "DefaultRaftPort": 10008, # raft port "RaftNodes": ["10.10.30.150", "10.10.30.128", "10.10.30.145"] start orchestrator to start the orchestrator service on each orchestrator machine. Cd / usr/local/orchestrator & &. / orchestrator-- config=/etc/orchestrator.conf.json http > / usr/local/orchestrator/orchestrator.log 2 > & 1 & the web-side access address 10.10.30.150virtual 3000. The effect of the page is as follows:

Here is the hypothetical environment:

10.10.30.170 is from the library

10.10.30.130 is the main library

As shown in the above figure

When version 3.1.2 orchestrator discovers the main database through the slave library 10.10.30.170, the master_host obtained through show slave status is 10.10.30.130, but the page shows the corresponding hostname:10-10-30-130 of the ip 10.10.30.130, as shown below:

Therefore, orchestrator will report that 10-10-30-130 cannot be found:

2019-11-27 13:48:29 ERROR dial tcp: lookup 10-10-30-130 on 223.5.5.5 on 53: no such host how to change the orchestrator version to 3.1.0 configure domain name resolution information under / etc/hosts on the orchestrator machine Add as follows: 10.10.30.130 10-10-30-13010.10.30.183 10-10-30-18310.10.30.170 10-10-30-170 on the MySQL high availability tool Orchestrator how to install raft multi-node mode is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.