CN112035435B - MySQL master-slave cluster installation and deployment method and cluster system - Google Patents

MySQL master-slave cluster installation and deployment method and cluster system Download PDF

Info

Publication number
CN112035435B
CN112035435B CN202010870488.9A CN202010870488A CN112035435B CN 112035435 B CN112035435 B CN 112035435B CN 202010870488 A CN202010870488 A CN 202010870488A CN 112035435 B CN112035435 B CN 112035435B
Authority
CN
China
Prior art keywords
slave
server
mysql
master
initializing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010870488.9A
Other languages
Chinese (zh)
Other versions
CN112035435A (en
Inventor
厉颖
赵山
王阳
高传集
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Inspur Cloud Information Technology Co Ltd
Original Assignee
Inspur Cloud Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Inspur Cloud Information Technology Co Ltd filed Critical Inspur Cloud Information Technology Co Ltd
Priority to CN202010870488.9A priority Critical patent/CN112035435B/en
Publication of CN112035435A publication Critical patent/CN112035435A/en
Application granted granted Critical
Publication of CN112035435B publication Critical patent/CN112035435B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Computing Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention discloses a MySQL master-slave cluster installation and deployment method and a cluster system, belongs to the technical field of cluster deployment and installation, and aims to solve the technical problem of how to automatically install and deploy MySQL clusters rapidly. The method comprises the following steps: deploying a server for installing MySQL, and verifying network connectivity of the server; preparing a data catalog/var/lib/mysql for each server, and initializing the data catalog/var/lib/mysql; initializing a user; initializing other running scripts for each server; setting a server MySQL configuration file; configuring a Slave node server of the Slave, and automatically synchronizing data between the Slave node server of the Slave and a Master node server; other running scripts for each server are started. The system comprises a plurality of servers, and MySQL master-slave clusters are installed and deployed through the method.

Description

MySQL master-slave cluster installation and deployment method and cluster system
Technical Field
The invention relates to the technical field of cluster deployment and installation, in particular to a MySQL master-slave cluster installation and deployment method and a cluster system.
Background
Under the background of cloud computing and big data, database application in public cloud environment is more and more widely used. The MySQL database is currently popular relational data, and in an actual production environment, the MySQL service of a single server cannot fully meet the actual requirements in consideration of various aspects such as safety, high availability and the like. Therefore, data is generally synchronized by Master-Slave replication (Master-Slave), and even if the Master node server is down, the server fails to start, and the data has no cold or hot backup, so that the data served by the Slave node is particularly important for data recovery.
After the MySQL service is installed, the master-slave cluster deployment of MySQL also needs to respectively carry out related configuration on the master-slave node servers, including data catalogues, users, master-slave plug-ins, master-slave configuration and the like, which are manually completed by professional technicians or operation and maintenance personnel.
Based on the analysis, how to install and deploy MySQL clusters quickly and automatically is a technical problem to be solved.
Disclosure of Invention
Aiming at the defects, the invention provides a MySQL master-slave cluster installation and deployment method and a cluster system, which are used for solving the problem of how to install and deploy MySQL clusters rapidly and automatically.
In a first aspect, the present invention provides a MySQL master-slave cluster installation and deployment method, which automatically installs and deploys MySQL master-slave clusters by executing Ansible scripts, the method comprising the following steps:
Deploying a server for installing MYSQL, and verifying the network connectivity of the server to determine Ansible that a script execution program is in network communication with the server, wherein at least one server;
preparing a data catalog/var/lib/mysql for each server, and initializing the data catalog/var/lib/mysql;
initializing a user, wherein the user is used for master-slave synchronization of a MySQL cluster;
initializing other running scripts for each server, including but not limited to monitoring function scripts;
setting a MySQL configuration file of a server, and respectively modifying the configuration files of a Master node server and a Slave node server;
configuring a Slave node server of the Slave, and automatically synchronizing data between the Slave node server of the Slave and a Master node server;
Other running scripts for each server are started.
Preferably, the server for installing MySQL master-slave clusters satisfies the following conditions:
the virtual machine mirror image is provided with MySQL services with the same version;
Servers of the same specification are created based on the same virtual machine image.
Preferably, preparing a data directory/var/lib/mysql for each server includes:
mounting a new disk to a target server, and performing fdisk disk partition;
Performing LVM logical volume management, wherein the logical volume is provided with a data catalog/var/lib/mysql catalog for specially storing the data catalog;
Initializing the data directory/var/lib/mysql, including: and initializing the MySQL data in a non-secure mode for the newly mounted data catalogue for anonymous login of the database.
Preferably, LOCAL SSD disks are mounted to the target server.
Preferably, initializing the user includes:
Initializing database users for creating master-slave synchronization, and giving REPLICATION SLAVE and REPLICATION CLIENT rights;
Database users for other functions including, but not limited to, monitoring database operating status are created, local users with localhost and 127.0.0.1 when initializing data directories are deleted, and non-secure anonymous users.
Preferably, the configuration Slave node server includes:
setting a server MySQL configuration file;
Accessing a Master node server at a Slave node server of the Slave, acquiring MySQL information of the Master node server, and recording the IP of the Master node server and the current binlog file name and position of the MySQL service;
Selectively stopping Slave on the Slave node servers of the Slave to ensure that the Slave node servers of the Slave do not perform master-Slave synchronization;
taking a binlog file and position information of a Master node server corresponding to MySQL service, and configuring Slave Master-Slave synchronization;
Master-slave synchronization is initiated and START SLAVE commands are executed.
Preferably, the server MySQL configuration file is set, which comprises the following steps:
Obtaining the specification of a server, and setting a parameter max_ connections and a parameter innodb _buffer_pool_size according to the performance specification, wherein the parameter max_ connections represents the maximum number of connectable connections, and the parameter innodb _buffer_pool_size represents the size of a data buffer pool;
setting server_ids of each server, wherein the server_ids of the servers are different from each other;
Starting the half-synchronous setting of the master-slave synchronization, wherein the half-synchronous setting comprises rpl_semi_sync_master_enabled, rpl_semi_sync_slave_enabled and rpl_semi_sync_master_timeout;
Setting a semi-synchronous plug-in configuration, i.e. plugin-load =
"Rpl_semi_sync_master= semisync _master. rpl_semi_sync_slave= semisync _slave.so ", so that when MySQL service is started, the master-slave plug-in can be automatically installed, and semi-synchronous replication is continuously used after the master-slave node service is switched, and the semi-synchronous plug-in is not installed by using independent insolation;
restarting MySQL service, the MySQL configuration takes effect.
Preferably, a different server_id is set for each server based on the characteristic that unix timestamp strings are not repeated.
In a second aspect, the present invention provides a cluster system, including a plurality of servers, where the MySQL master-slave cluster installation deployment method according to any one of the first aspects is applied to install and deploy MySQL master-slave clusters.
The MySQL master-slave cluster installation and deployment method and the cluster system have the following advantages:
1. The database cluster script is built through Ansible script batch execution, server IP of a master-slave cluster is deployed on configuration, and a written Ansible command is executed, so that MySQL master-slave cluster functions can be built through one key, deployment can be completed quickly, automatic completion is achieved to the greatest extent, service response capability is improved, cost is reduced, installation and deployment efficiency of the MySQL master-slave cluster is improved, and feasibility is high;
2. Carrying out automatic installation and deployment in batches by Ansible, synchronously setting MySQL configuration files by using different Master and Slave role servers of MySQL Master-Slave clusters, and setting Master-Slave MySQL data synchronization by using a split role Slave server, thereby reducing the complexity of manual operation and improving the deployment efficiency;
3. Setting the maximum connection number and innodb cache configuration of MySQL according to different server specifications, and maximally utilizing the configuration of the server to improve MySQL service performance;
4. Setting different server_ids for each server by utilizing the characteristic that unix timestamp character strings are not repeated, ensuring that the configuration of the servers is different, and eliminating the master-slave synchronization problem caused by the fact that the server_ids are the same for the master server and the slave server;
5. And the configuration of the semi-synchronous plug-in is set, so that the master-slave plug-in can be automatically installed when the MySQL service is started, and the semi-synchronous replication is continuously used after the master-slave node service is switched.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments or the description of the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
The invention is further described below with reference to the accompanying drawings.
FIG. 1 is a flow chart of a MySQL master-slave cluster installation deployment method of embodiment 1;
FIG. 2 is a block flow diagram of a MySQL configuration file of a setup server in a MySQL master-slave cluster installation deployment method of embodiment 1;
Fig. 3 is a flow chart of a Slave node server configuration Slave node in the MySQL master-Slave cluster installation deployment method of embodiment 1.
Detailed Description
The invention will be further described with reference to the accompanying drawings and specific examples, so that those skilled in the art can better understand the invention and implement it, but the examples are not meant to limit the invention, and the technical features of the embodiments of the invention and the examples can be combined with each other without conflict.
It should be understood that "plurality" in the embodiments of the present invention means two or more.
The embodiment of the invention provides a MySQL master-slave cluster installation and deployment method and a cluster system, which are used for solving the technical problem of how to automatically install and deploy MySQL clusters rapidly.
Examples:
Ansible is an automated operation tool, which can implement functions such as batch system configuration, batch program deployment, batch operation command, etc. MySQL master-slave clusters are automatically installed and deployed by executing and writing Ansible scripts, so that one-key deployment is realized, and the risk of manual misoperation of each server is reduced.
The invention relates to a MySQL master-slave cluster installation and deployment method, which automatically installs and deploys MySQL master-slave clusters by executing Ansible scripts, and comprises the following steps:
S100, deploying a server for installing MySQL, and verifying network connectivity of the server to determine Ansible script execution programs to be communicated with the server network, wherein at least one server is used;
S200, preparing a data catalog/var/lib/mysql for each server, and initializing the data catalog/var/lib/mysql;
S300, initializing a user, wherein the user is used for master-slave synchronization of a MySQL cluster;
s400, initializing other operation scripts for each server, wherein the other operation scripts comprise but are not limited to monitoring function scripts;
s500, setting a MySQL configuration file of a server, and respectively modifying the configuration files of a Master node server and a Slave node server;
S600, configuring a Slave node server of the Slave, and automatically synchronizing data between the Slave node server of the Slave and a Master node server;
s700, starting other running scripts of each server.
The server for deploying and installing the MySQL master-slave cluster needs to meet the following advanced conditions: the virtual machine mirror image is provided with MySQL services with the same version; servers of the same specification are created based on the same virtual machine image.
Preparing a data catalog/var/lib/mysql for each server, comprising the steps of:
(1) Mounting a new disk to a target server, performing fdisk disk partition, and mounting a LOCAL SSD disk to the target server in the embodiment;
(2) And performing LVM logical volume management, wherein the logical volume is provided with a data catalog/var/lib/mysql catalog for storing the data catalog specially.
Initializing the data directory/var/lib/mysql, including: and initializing the MySQL data in a non-secure mode for the newly mounted data catalogue for anonymous login of the database.
In step S300, each server starts MySQL database and initializes the user. The initializing user comprises the following operations: initializing and creating database users for master-slave synchronization, giving the REPLICATION SLAVE, REPLICATION CLIENT rights, simultaneously creating database users for other functions such as monitoring the running state of the database, deleting local users of self-contained localhost and 127.0.0.1 when initializing a data directory, and unsafe anonymous users.
In step S400, a server MySQL configuration file is set, which includes the following steps:
S410, obtaining the specification of a server, and setting a parameter max_ connections and a parameter innodb _buffer_pool_size according to the performance specification, wherein the parameter max_ connections represents the maximum number of connectable connections, and the parameter innodb _buffer_pool_size represents the size of a data buffer pool;
S420, setting server_ids of each server, wherein the server_ids of the servers are different from each other, and if the server_ids of the Master server and the Slave servers are consistent, synchronous replication fails, so that the server_ids need to be set differently;
S430, starting the half-synchronous setting of the master-slave synchronization, wherein the half-synchronous setting comprises rpl_semi_sync_master_enable-d, rpl_semi_sync_slave_enable and rpl_semi_sync_master_timeout;
S440, a semi-synchronous plug-in configuration is set, i.e. plug in-load =
"Rpl_semi_sync_master= semisync _master. rpl_semi_sync_slave= semisync _slave.so ", so that when MySQL service is started, the master-slave plug-in can be automatically installed, and semi-synchronous replication is continuously used after the master-slave node service is switched, and the semi-synchronous plug-in is not installed by using independent insolation;
s450, restarting the MySQL service, wherein the MySQL configuration takes effect.
The configuration Slave node server comprises the following steps:
S510, setting a server MySQL configuration file according to the step S400;
S520, accessing a Master node server at the Slave node server, acquiring MySQL information of the Master node server, and recording the IP of the Master node server and the current binlog file name and position of the MySQL service;
s530, selectively stopping Slave on the Slave node server of the Slave to ensure that the Slave node server of the Slave does not perform master-Slave synchronization;
s540, taking a binlog file and position information of a Master node server corresponding to MySQL service, and configuring Slave Master-Slave synchronization;
S550, starting master-slave synchronization and executing START SLAVE commands.
According to the MySQL Master-Slave cluster installation and deployment method, ansible is adopted for carrying out automatic installation and deployment in batches, mySQL configuration files are synchronously set by different Master and Slave role servers of the MySQL Master-Slave clusters, master-Slave MySQL data synchronization is set by the split role Slave servers, the complexity of manual operation is reduced, and the deployment efficiency is improved; setting the maximum connection number and innodb cache configuration of MySQL according to different server specifications, and maximally utilizing the configuration of the server to improve MySQL service performance; setting different server_ids for each server by utilizing the characteristic that unix timestamp character strings are not repeated, ensuring that the configuration of the servers is different, and eliminating the master-slave synchronization problem caused by the fact that the server_ids are the same for the master server and the slave server; and the configuration of the semi-synchronous plug-in is set, so that the master-slave plug-in can be automatically installed when the MySQL service is started, and the semi-synchronous replication is continuously used after the master-slave node service is switched.
Example 2:
the cluster system comprises a plurality of servers, and MySQL master-slave clusters are installed and deployed by the cluster system application MySQL master-slave cluster installation and deployment method disclosed by the embodiment 1.
While the invention has been illustrated and described in detail in the drawings and in the preferred embodiments, the invention is not limited to the disclosed embodiments, and it will be appreciated by those skilled in the art that the code audits of the various embodiments described above may be combined to produce further embodiments of the invention, which are also within the scope of the invention.

Claims (3)

  1. The MySQL master-slave cluster installation and deployment method is characterized by automatically installing and deploying MySQL master-slave clusters by executing Ansible scripts, and comprises the following steps of:
    Deploying a server for installing MySQL, and verifying network connectivity of the server to determine Ansible that a script execution program is in network communication with the server, wherein at least one server;
    preparing a data catalog/var/lib/mysql for each server, and initializing the data catalog/var/lib/mysql;
    initializing a user, wherein the user is used for master-slave synchronization of a MySQL cluster;
    Initializing other operation scripts for each server, wherein the other operation scripts comprise monitoring function scripts;
    setting a MySQL configuration file of a server, and respectively modifying the configuration files of a Master node server and a Slave node server;
    configuring a Slave node server of the Slave, and automatically synchronizing data between the Slave node server of the Slave and a Master node server;
    Starting other running scripts of each server;
    Preparing a data catalog/var/lib/mysql for each server, comprising:
    mounting a new disk to a target server, and performing fdisk disk partition;
    Performing LVM logical volume management, wherein the logical volume is provided with a data catalog/var/lib/mysql catalog for specially storing the data catalog;
    Initializing the data directory/var/lib/mysql, including: initializing non-secure mode MySQL data for a newly mounted data directory for anonymous login of a database;
    Mounting a LOCAL SSD disk to a target server;
    Initializing a user, comprising:
    Initializing database users for creating master-slave synchronization, and giving REPLICATION SLAVE and REPLICATION CLIENT rights;
    Creating database users for other functions including monitoring database operating status, deleting local users that are self-contained and 127.0.0.1 when initializing the data directory, and non-secure anonymous users;
    Configuring a Slave node server includes:
    setting a server MySQL configuration file;
    Accessing a Master node server at a Slave node server of the Slave, acquiring MySQL information of the Master node server, and recording the IP of the Master node server and the current binlog file name and position of the MySQL service;
    Selectively stopping Slave on the Slave node servers of the Slave to ensure that the Slave node servers of the Slave do not perform master-Slave synchronization;
    taking a binlog file and position information of a Master node server corresponding to MySQL service, and configuring Slave Master-Slave synchronization;
    starting master-slave synchronization and executing START SLAVE commands;
    setting a server MySQL configuration file, comprising the following steps:
    Obtaining the specification of a server, and setting a parameter max_ connections and a parameter innodb _buffer_pool_size according to the performance specification, wherein the parameter max_ connections represents the maximum number of connectable connections, and the parameter innodb _buffer_pool_size represents the size of a data buffer pool;
    setting server_ids of each server, wherein the server_ids of the servers are different from each other;
    Starting the half-synchronous setting of the master-slave synchronization, wherein the half-synchronous setting comprises rpl_semi_sync_master_enabled, rpl_semi_sync_slave_enabled and rpl_semi_sync_master_timeout;
    Setting a semi-synchronous plug-in configuration, i.e. plugin-load =
    Rpl_semi_sync_master= semisync _master.so, rpl_semi_sync_slave= semisync _slave.so, so that a master-slave plug-in can be automatically installed when MySQL service is started, semi-synchronous replication is continuously used after the master-slave node service is switched, and the semi-synchronous plug-in is installed without independent instal;
    restarting MySQL service, wherein the MySQL configuration takes effect;
    Based on the non-repeating property of unix timestamp strings, a different server_id is set for each server.
  2. 2. The MySQL master-slave cluster installation deployment method according to claim 1, wherein the server for installing MySQL master-slave clusters satisfies the following condition:
    the virtual machine mirror image is provided with MySQL services with the same version;
    Servers of the same specification are created based on the same virtual machine image.
  3. 3. The cluster system comprises a plurality of servers, and is characterized in that the MySQL master-slave cluster installation and deployment method is applied to the cluster system, and MySQL master-slave clusters are installed and deployed by the method according to any one of claims 1-2.
CN202010870488.9A 2020-08-26 2020-08-26 MySQL master-slave cluster installation and deployment method and cluster system Active CN112035435B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010870488.9A CN112035435B (en) 2020-08-26 2020-08-26 MySQL master-slave cluster installation and deployment method and cluster system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010870488.9A CN112035435B (en) 2020-08-26 2020-08-26 MySQL master-slave cluster installation and deployment method and cluster system

Publications (2)

Publication Number Publication Date
CN112035435A CN112035435A (en) 2020-12-04
CN112035435B true CN112035435B (en) 2024-04-30

Family

ID=73581532

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010870488.9A Active CN112035435B (en) 2020-08-26 2020-08-26 MySQL master-slave cluster installation and deployment method and cluster system

Country Status (1)

Country Link
CN (1) CN112035435B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112667440A (en) * 2020-12-28 2021-04-16 紫光云技术有限公司 Long-distance disaster recovery method for high-availability MySQL
CN113138882B (en) * 2021-05-12 2023-02-07 深圳赛安特技术服务有限公司 MySQL cluster-based automatic deployment method and device and related equipment
CN114024841B (en) * 2021-08-04 2023-09-19 统信软件技术有限公司 Server cluster deployment method and device, computing equipment and storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015188617A1 (en) * 2014-06-11 2015-12-17 中兴通讯股份有限公司 Method and device for installing mysql databases
CN105204897A (en) * 2015-09-14 2015-12-30 上海新炬网络信息技术有限公司 Batched MySQL installation and deployment method
CN107861838A (en) * 2017-10-18 2018-03-30 福建中金在线信息科技有限公司 Method and device of the automated back-up MySQL database from storehouse
CN109104318A (en) * 2018-08-23 2018-12-28 广东轩辕网络科技股份有限公司 The dispositions method and system of method for realizing cluster self-adaption deployment, the self-adaption deployment big data cluster based on cloud platform
WO2019101095A1 (en) * 2017-11-21 2019-05-31 北京金山云网络技术有限公司 Node down recovery method and apparatus, electronic device, and storage medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8572031B2 (en) * 2010-12-23 2013-10-29 Mongodb, Inc. Method and apparatus for maintaining replica sets

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015188617A1 (en) * 2014-06-11 2015-12-17 中兴通讯股份有限公司 Method and device for installing mysql databases
CN105204897A (en) * 2015-09-14 2015-12-30 上海新炬网络信息技术有限公司 Batched MySQL installation and deployment method
CN107861838A (en) * 2017-10-18 2018-03-30 福建中金在线信息科技有限公司 Method and device of the automated back-up MySQL database from storehouse
WO2019101095A1 (en) * 2017-11-21 2019-05-31 北京金山云网络技术有限公司 Node down recovery method and apparatus, electronic device, and storage medium
CN109104318A (en) * 2018-08-23 2018-12-28 广东轩辕网络科技股份有限公司 The dispositions method and system of method for realizing cluster self-adaption deployment, the self-adaption deployment big data cluster based on cloud platform

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
彭剑 ; 刘艳松 ; 唐闻 ; .MySQL主从服务器数据库同步的实现.福建电脑.2020,(07),全文. *
李海兵 ; .基于MySQL的负载均衡的搭建与研究.信息安全与技术.2011,(05),全文. *

Also Published As

Publication number Publication date
CN112035435A (en) 2020-12-04

Similar Documents

Publication Publication Date Title
CN112035435B (en) MySQL master-slave cluster installation and deployment method and cluster system
US11907254B2 (en) Provisioning and managing replicated data instances
CN111522628B (en) Kubernetes cluster building deployment method, framework and storage medium based on OpenStack
CN107566165B (en) Method and system for discovering and deploying available resources of power cloud data center
WO2017162173A1 (en) Method and device for establishing connection of cloud server cluster
TW202403565A (en) Automatically deployed information technology (it) system and method
EP1701263B1 (en) Computer system and data backup method in computer system
CN102591679A (en) Quick application software arrangement method for cluster system
CN106254127A (en) Automatic deployment method of RabbitMQ cluster service based on virtualization platform
CN114270779A (en) Automatically deployed Information Technology (IT) system and method with enhanced security
CN111651275A (en) MySQL cluster automatic deployment system and method
CN104572269A (en) Quick cluster deployment method based on Linux operation system
CN111786810A (en) Automatic deployment method and system for large-scale test bed nodes
CN105007290A (en) Linux system remote installation configuration management method aiming at disk-free server
CN112199157A (en) Cloud environment management method
CN111343011B (en) Openstack network fusion control method and system for cloud management platform
CN105159799A (en) Method and device for backing up server
CN106980493A (en) Firmware management method and apparatus
CN101453473A (en) Remote service system based on different operation systems and equipment thereof
CN108062225B (en) Method for issuing application cluster by multi-template combination
CN114443073A (en) Device and method for rapidly deploying bare metal server
CN104063294B (en) A kind of linux system backup and restoration methods
CN106209445A (en) A kind of Visualized data centre by network design
WO2006043309A1 (en) Operation management program, operation management method, and operation management apparatus
CN110928624A (en) Cloud desktop calling method and device for user terminal and terminal

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant