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

In this issue, the editor will bring you about how to deploy MySQL replication topology management tool Orchestrator. The article is rich in content and analyzes and describes for you from a professional point of view. I hope you can get something after reading this article.

Today we will focus on how to deploy the MySQL replication topology management tool-- Orchestrator.

MySQL replication Topology Management tool Orchestrator

1. Brief introduction

Orchestrator is an open source MySQL replication topology management tool, written in go language, which supports the adjustment of MySQL master-slave replication topology, automatic failure switching of MySQL master library, manual master-slave switching and other functions.

The Orchestrator backend relies on MySQL or SQLite to store metadata, and can provide Web interface to display the topology relationship and instance status of MySQL cluster. Through the Web interface, you can change part of the configuration information of MySQL instance. It also provides command line and api interface for more flexible automatic operation and maintenance management.

Compared with MHA,Orchestrator, it pays more attention to the management of replication topology, and can adjust any replication topology of MySQL. On this basis, MySQL can be highly available. In addition, Orchestrator itself can deploy multiple nodes to ensure its own high availability through raft distributed consistency protocol.

two。 Features

Orchestrato has the following main characteristics:

Automatically monitor the structure and status of database replication

GUI,CLI,API and other interfaces are provided to check the status of the replication topology and make some adjustments.

Automatic master failover is supported. When the server of the replication structure is down (whether manual or automatic), the replication topology can be reformed.

Does not depend on a specific server version or branch (MySQL, Percona Server, MariaDB or even MaxScale binlog servers)

Supports multiple types of topologies, whether it is a single master-slave or multi-level replication consisting of hundreds of server

His GUI doesn't just report the topology status to you, you can change the replication topology by dragging or deleting nodes on the Orchestrator web page (CLI and API can also do this)

3. System structure

The following chart illustrates each Orchestrator function and how it communicates with each other.

The Orchestration database is the center of the Orchestrator installation and contains all Runbook, configuration settings, and logs. The system needs to use Management server as the communication layer between Runbook Designer and Orchestration database. One or more Runbook servers communicate directly with this database to retrieve the Runbook to run and to store information about jobs created from Runbook. The Web service also communicates directly with the Orchestration database and provides a Web browser connection to the Orchestration console.

II. Environmental preparation

1. IP planning

two。 Set up hostname resolution

3. Install and deploy Orchestrator

Source code address: https://github.com/github/orchestrator.git

1. download

2. Rpm installation

After the installation is complete, the directory is in / usr/local/orchestrator

3. Modify my.cnf

A report_host parameter is added to the MySQL configuration file. Report_host is read-only and must be restarted to take effect.

Note: without report_host, show slave hosts will not display host, which will cause the program to report an error

4. Create databases and users

(1) Topology library operation:

CREATE DATABASE IF NOT EXISTS orchestrator; GRANT ALL PRIVILEGES ON `orchestrator. * TO 'orche'@'%' IDENTIFIED BY' xxxxx'

(2) Master / slave library operation:

If it is a master-slave replication, the master-slave will operate separately.

5. Modify orchestrator configuration file

# cd / usr/local/orchestrator/ # cp orchestrator-sample.conf.json orchestrator.conf.json # vim orchestrator.conf.json = = {"Debug": true, "EnableSyslog": false, "ListenAddress": ": 3000", # http Open Port "MySQLTopologyUser": "orche", # mysql Management account All managed MySQL clusters need this account "MySQLTopologyPassword": "xx", # mysql management account password "MySQLTopologyCredentialsConfigFile": "", "MySQLTopologySSLPrivateKeyFile": "", "MySQLTopologySSLCertFile": "", "MySQLTopologySSLCAFile": "", "MySQLTopologySSLSkipVerify": true, "MySQLTopologyUseMutualTLS": false, "MySQLOrchestratorHost": "xx", # backend mysql database address Orchestrator relies on MySQL or SQLite to store and manage data "MySQLOrchestratorPort": 3306, # background mysql database port "MySQLOrchestratorDatabase": "orchestrator", # background mysql database name "MySQLOrchestratorUser": "orche", # background mysql database account "MySQLOrchestratorPassword": "xx", # background mysql database password. ] =

Note: the MySQLTopologyUser configuration item is the admin account of the managed MySQL cluster, which requires super,process,reload,select,replicatiopn slave,replicatiopn client permission.

6. Start orchestrator

7. Discover an example

8. Visit

Web page: http://172.26.151.69:3000

At this point, the construction of orchestrator is completed.

The above is the editor for you to share how to deploy MySQL replication topology management tool Orchestrator, if you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

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.