CN116760693B - Method and system for switching main and standby nodes of database - Google Patents
Method and system for switching main and standby nodes of database Download PDFInfo
- Publication number
- CN116760693B CN116760693B CN202311041002.0A CN202311041002A CN116760693B CN 116760693 B CN116760693 B CN 116760693B CN 202311041002 A CN202311041002 A CN 202311041002A CN 116760693 B CN116760693 B CN 116760693B
- Authority
- CN
- China
- Prior art keywords
- node
- switching
- standby
- nodes
- database
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 230000002159 abnormal effect Effects 0.000 claims abstract description 12
- 230000005856 abnormality Effects 0.000 claims description 3
- 238000004891 communication Methods 0.000 claims description 3
- 230000003068 static effect Effects 0.000 claims description 3
- 230000001360 synchronised effect Effects 0.000 claims description 3
- 230000001960 triggered effect Effects 0.000 claims description 3
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- 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
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0614—Improving the reliability of storage systems
- G06F3/0619—Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Hardware Redundancy (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a method and a system for switching main and standby nodes of a database, comprising the following steps: s1, creating and deploying a switching execution component and a switching judgment component, acquiring the node state of each node, and starting the switching of the master node and the slave node when the node state is abnormal; s2, the switching judging component sends a Lock command to Lock the write operation of the master and slave nodes of the database, and after the write operation of all the nodes is locked, the master and slave node switching is continued; s3, selecting a standby node to replace the current main node according to the log sequence number by the switching judging component, sending the node information of the new main node to the rest standby nodes, unlocking the writing operation of all the nodes, and finishing the switching of the main node and the standby node. The application has the beneficial effects that: if the main node of the database is abnormal, before a standby node is selected to take over the cluster, a candidate node which is truly identical with the old main data of the database is selected through locking the writing operation of the database, so that the data after switching is ensured not to be lost.
Description
Technical Field
The application belongs to the field of database operation and maintenance, and particularly relates to a method and a system for switching main and standby nodes of a database.
Background
In the database master-slave cluster, when the master node fails or the network has a problem, in order to ensure high availability of the database, one of the slave nodes needs to be selected as a new master node to provide service.
In order to ensure that the data is not lost after the switching, the data of the selected standby node and the data of the main node are required to be completely consistent, and in order to achieve the condition, the standby with the largest LSN is generally selected as the candidate standby by acquiring the LSN of the received data logs of all the standby nodes.
But for two reasons: 1) There may be a time difference in the messages of the acquisition backup log lSN; 2) If the old master is due to a network problem, due to the complexity of networking, it is possible that the master node is synchronizing data to some standby nodes; the standby node with the largest acquired log LSN may not be completely consistent with the data of the main node, so that the data may be lost after the switching, which is an absolutely unacceptable fatal defect for systems with high requirements on data consistency, such as banks and securities.
Disclosure of Invention
In view of the above, the present application is directed to a method and a system for switching active/standby nodes of a database, so as to solve at least one of the above technical problems.
In order to achieve the above purpose, the technical scheme of the application is realized as follows:
the first aspect of the present application provides a method for switching between active and standby nodes of a database, comprising the following steps:
s1, creating and deploying a switching execution component and a switching judgment component, acquiring node states of all nodes, and starting a database master-slave node switching flow when the node states are abnormal;
s2, the switching judging component sends a Lock command to the switching executing component to Lock the writing operation of the main and standby nodes of the database, and after the writing operation of all the nodes is locked, the switching process of the main and standby nodes of the database is continuously executed;
s3, selecting a standby node to replace the current main node according to the log sequence number by the switching judging component, sending the node information of the new main node to the rest standby nodes, unlocking write operations of all nodes, and ending the switching flow of the main and standby nodes of the database.
Further, the specific process of step S1 is as follows:
s101, creating and deploying a switching execution component on a server where each node is located, and acquiring a node state of the corresponding node;
s102, creating a switching judgment component, establishing data connection between the switching judgment component and a switching execution component, and sending the acquired node state to the switching judgment component by the switching execution component;
s103, the switching judgment component receives and identifies the node state, and when the node state is abnormal, the switching judgment component starts the switching process of the main and standby nodes of the database.
Further, the specific process of step S2 is as follows:
s201, the switching judging component sends Lock commands to all the switching executing components, and after receiving the commands, the switching executing components Lock write operations of the corresponding nodes;
s202, the switching execution component sends the information that the writing operation of the corresponding node is locked to the switching judgment component;
s203, the switching judgment component receives and counts the information sent by each switching execution component in real time, and executes the subsequent database active/standby node switching flow after all nodes are in a writing operation locking state.
Further, the specific process of step S3 is as follows:
s301, a switching execution component acquires a log sequence number in a database write log and uploads the log sequence number to a switching judgment component;
s302, the switching judgment component selects the standby node with the largest log sequence number as a candidate main node, informs the candidate main node and executes the operation of switching the standby node to the main node;
s303, the candidate master node receives the notification and feeds back the current preparation state to the switching execution component;
s304, the switching execution component informs the current master node of the database to execute the operation of switching the master node to the standby node, and simultaneously, the switching execution component sends the node information of the new master node to all other standby nodes;
s305, the switching judging component sends an unlock command to all the switching executing components to unlock the write operation of all the nodes.
The second aspect of the present application provides a system for switching between active and standby nodes of a database, which is characterized in that:
comprising the following steps:
the switching judgment module monitors the node state of the main node in the database cluster in real time, and when the main node is abnormal, the switching judgment module sends a switching flow command;
the switching execution module monitors the node states of all nodes in the database cluster in real time and sends the monitored node state information to the switching judgment module in real time;
the switching execution module is positioned in a server where the database is positioned and establishes communication connection with the corresponding node;
the switching execution module executes the lock, unlock, standby node to master node and master node to standby node commands issued by the switching judgment module, and reports the node state in real time for the switching judgment module to use.
Further, the switching decision module detects the node state of the master node in the database cluster, and if abnormality occurs, the switching process is triggered;
the switching judgment module sends a lock command to all the standby nodes in the database cluster, and the standby nodes do not accept the data synchronization of the main nodes after receiving the lock command;
when all the standby nodes are successfully locked, the data of the main node cannot be synchronized to the standby nodes, the data in the main node is not pushed any more, the main node is in a writing static state, in this state, a switching judgment module acquires the data LSN of all the standby nodes, selects the standby node with the largest LSN as a candidate main node, and triggers the standby node to switch to the main node;
and after the standby node changes the main node successfully, an unlock notification is sent to all the nodes.
Compared with the prior art, the method and the system for switching the master node and the slave node of the database have the following beneficial effects:
according to the method and the system for switching the main and the standby nodes of the database, if the main node of the database is abnormal, before one standby node is selected to take over the cluster, the database is in a write-lock state through the lock database cluster, so that the selection of a candidate node which is truly identical with the old main data of the database can be facilitated, and the data after switching is ensured not to be lost.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings:
fig. 1 is a schematic workflow diagram of a database active/standby node switching method according to an embodiment of the present application;
FIG. 2 is a schematic diagram illustrating the operation of step S1 according to an embodiment of the present application;
FIG. 3 is a schematic diagram illustrating the operation of step S2 according to an embodiment of the present application;
fig. 4 is a schematic diagram illustrating the operation of step S3 according to an embodiment of the present application.
Detailed Description
It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other.
The application will be described in detail below with reference to the drawings in connection with embodiments.
A method for switching database master and slave nodes includes the following steps:
s1, creating and deploying a switching execution component and a switching judgment component, acquiring node states of all nodes, and starting a database master-slave node switching flow when the node states are abnormal;
the specific process of step S1 is as follows:
s101, creating and deploying a switching execution component on a server where each node is located, and acquiring a node state of the corresponding node;
s102, creating a switching judgment component, establishing data connection between the switching judgment component and a switching execution component, and sending the acquired node state to the switching judgment component by the switching execution component;
s103, the switching judgment component receives and identifies the node state, and when the node state is abnormal, the switching judgment component starts the switching process of the main and standby nodes of the database.
S2, the switching judging component sends a Lock command to the switching executing component to Lock the writing operation of the main and standby nodes of the database, and after the writing operation of all the nodes is locked, the switching process of the main and standby nodes of the database is continuously executed;
the specific process of step S2 is as follows:
s201, the switching judging component sends Lock commands to all the switching executing components, and after receiving the commands, the switching executing components Lock write operations of the corresponding nodes;
s202, the switching execution component sends the information that the writing operation of the corresponding node is locked to the switching judgment component;
s203, the switching judgment component receives and counts the information sent by each switching execution component in real time, and executes the subsequent database active/standby node switching flow after all nodes are in a writing operation locking state.
S3, selecting a standby node to replace the current main node according to the log sequence number by the switching judging component, sending the node information of the new main node to the rest standby nodes, unlocking write operations of all nodes, and ending the switching flow of the main and standby nodes of the database.
The specific process of step S3 is as follows:
s301, a switching execution component acquires a log sequence number in a database write log and uploads the log sequence number to a switching judgment component;
s302, the switching judgment component selects the standby node with the largest log sequence number as a candidate main node, informs the candidate main node and executes the operation of switching the standby node to the main node;
s303, the candidate master node receives the notification and feeds back the current preparation state to the switching execution component;
s304, the switching execution component informs the current master node of the database to execute the operation of switching the master node to the standby node, and simultaneously, the switching execution component sends the node information of the new master node to all other standby nodes;
s305, the switching judging component sends an unlock command to all the switching executing components to unlock the write operation of all the nodes.
A system for a database active-standby node switching method includes:
the switching judgment module monitors the node state of the main node in the database cluster in real time, and when the main node is abnormal, the switching judgment module sends a switching flow command;
the switching execution module monitors the node states of all nodes in the database cluster in real time and sends the monitored node state information to the switching judgment module in real time;
the switching execution module is positioned in a server where the database is positioned and establishes communication connection with the corresponding node;
the switching execution module executes the lock, unlock, standby node to master node and master node to standby node commands issued by the switching judgment module, and reports the node state in real time for the switching judgment module to use.
The switching decision module detects the node state of the main node in the database cluster, and if abnormality occurs, the switching flow is triggered;
the switching judgment module sends a lock command to all the standby nodes in the database cluster, and the standby nodes do not accept the data synchronization of the main nodes after receiving the lock command;
when all the standby nodes are successfully locked, the data of the main node cannot be synchronized to the standby nodes, the data in the main node is not pushed any more, the main node is in a writing static state, in this state, a switching judgment module acquires the data LSN of all the standby nodes, selects the standby node with the largest LSN as a candidate main node, and triggers the standby node to switch to the main node;
and after the standby node changes the main node successfully, an unlock notification is sent to all the nodes.
Those of ordinary skill in the art will appreciate that the elements and method steps of each example described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the elements and steps of each example have been described generally in terms of functionality in the foregoing description to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the several embodiments provided in the present application, it should be understood that the disclosed methods and systems may be implemented in other ways. For example, the above-described division of units is merely a logical function division, and there may be another division manner when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted or not performed. The units may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment of the present application.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application, and are intended to be included within the scope of the appended claims and description.
The foregoing description of the preferred embodiments of the application is not intended to be limiting, but rather is intended to cover all modifications, equivalents, alternatives, and improvements that fall within the spirit and scope of the application.
Claims (6)
1. A method for switching the main and standby nodes of a database is characterized in that:
the method comprises the following steps:
s1, creating and deploying a switching execution component and a switching judgment component, acquiring node states of all nodes, and starting a database master-slave node switching flow when the node states are abnormal;
s2, the switching judging component sends a Lock command to the switching executing component to Lock the writing operation of the main and standby nodes of the database, and after the writing operation of all the nodes is locked, the switching process of the main and standby nodes of the database is continuously executed;
s3, selecting a standby node to replace the current main node according to the log sequence number by the switching judging component, sending the node information of the new main node to the rest standby nodes, unlocking write operations of all nodes, and ending the switching flow of the main and standby nodes of the database.
2. The method for switching between the active node and the standby node of the database according to claim 1, wherein the method comprises the following steps:
the specific process of step S1 is as follows:
s101, creating and deploying a switching execution component on a server where each node is located, and acquiring a node state of the corresponding node;
s102, creating a switching judgment component, establishing data connection between the switching judgment component and a switching execution component, and sending the acquired node state to the switching judgment component by the switching execution component;
s103, the switching judgment component receives and identifies the node state, and when the node state is abnormal, the switching judgment component starts the switching process of the main and standby nodes of the database.
3. The method for switching between the active node and the standby node of the database according to claim 1, wherein the method comprises the following steps:
the specific process of step S2 is as follows:
s201, the switching judging component sends Lock commands to all the switching executing components, and after receiving the commands, the switching executing components Lock write operations of the corresponding nodes;
s202, the switching execution component sends the information that the writing operation of the corresponding node is locked to the switching judgment component;
s203, the switching judgment component receives and counts the information sent by each switching execution component in real time, and executes the subsequent database active/standby node switching flow after all nodes are in a writing operation locking state.
4. The method for switching between the active node and the standby node of the database according to claim 1, wherein the method comprises the following steps:
the specific process of step S3 is as follows:
s301, a switching execution component acquires a log sequence number in a database write log and uploads the log sequence number to a switching judgment component;
s302, the switching judgment component selects the standby node with the largest log sequence number as a candidate main node, informs the candidate main node and executes the operation of switching the standby node to the main node;
s303, the candidate master node receives the notification and feeds back the current preparation state to the switching execution component;
s304, the switching execution component informs the current master node of the database to execute the operation of switching the master node to the standby node, and simultaneously, the switching execution component sends the node information of the new master node to all other standby nodes;
s305, the switching judging component sends an unlock command to all the switching executing components to unlock the write operation of all the nodes.
5. A system for applying the method for switching between the active and standby nodes of the database as claimed in claim 1, characterized in that:
the system comprises:
the switching judgment module monitors the node state of the main node in the database cluster in real time, and when the main node is abnormal, the switching judgment module sends a switching flow command;
the switching execution module monitors the node states of all nodes in the database cluster in real time and sends the monitored node state information to the switching judgment module in real time;
the switching execution module is positioned in a server where the database is positioned and establishes communication connection with the corresponding node;
the switching execution module executes the lock, unlock, standby node to master node and master node to standby node commands issued by the switching judgment module, and reports the node state in real time for the switching judgment module to use.
6. The system for switching between active and standby nodes of a database according to claim 5, wherein:
the switching decision module detects the node state of the main node in the database cluster, and if abnormality occurs, the switching flow is triggered;
the switching judgment module sends a lock command to all the standby nodes in the database cluster, and the standby nodes do not accept the data synchronization of the main nodes after receiving the lock command;
when all the standby nodes are successfully locked, the data of the main node cannot be synchronized to the standby nodes, the data in the main node is not pushed any more, the main node is in a writing static state, in this state, a switching judgment module acquires the data LSN of all the standby nodes, selects the standby node with the largest LSN as a candidate main node, and triggers the standby node to switch to the main node;
and after the standby node changes the main node successfully, an unlock notification is sent to all the nodes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311041002.0A CN116760693B (en) | 2023-08-18 | 2023-08-18 | Method and system for switching main and standby nodes of database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311041002.0A CN116760693B (en) | 2023-08-18 | 2023-08-18 | Method and system for switching main and standby nodes of database |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116760693A CN116760693A (en) | 2023-09-15 |
| CN116760693B true CN116760693B (en) | 2023-10-27 |
Family
ID=87953668
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311041002.0A Active CN116760693B (en) | 2023-08-18 | 2023-08-18 | Method and system for switching main and standby nodes of database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116760693B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013076819A1 (en) * | 2011-11-22 | 2013-05-30 | 株式会社Ｍｕｒａｋｕｍｏ | Database management method |
| CN115237674A (en) * | 2022-07-19 | 2022-10-25 | 浪潮思科网络科技有限公司 | Data backup method, device and medium for SDN controller based on opennaylight |
| CN115858236A (en) * | 2021-09-23 | 2023-03-28 | 华为技术有限公司 | Data backup method and database cluster |
| CN115934742A (en) * | 2022-12-26 | 2023-04-07 | 上海浦东发展银行股份有限公司 | Fault processing method, device, equipment and storage medium |
| CN116107814A (en) * | 2023-04-04 | 2023-05-12 | 阿里云计算有限公司 | Database disaster recovery method, equipment, system and storage medium |
| CN116126832A (en) * | 2023-02-09 | 2023-05-16 | 平安付科技服务有限公司 | Database switching method, switching device, electronic equipment and storage medium |
-
2023
- 2023-08-18 CN CN202311041002.0A patent/CN116760693B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013076819A1 (en) * | 2011-11-22 | 2013-05-30 | 株式会社Ｍｕｒａｋｕｍｏ | Database management method |
| CN115858236A (en) * | 2021-09-23 | 2023-03-28 | 华为技术有限公司 | Data backup method and database cluster |
| CN115237674A (en) * | 2022-07-19 | 2022-10-25 | 浪潮思科网络科技有限公司 | Data backup method, device and medium for SDN controller based on opennaylight |
| CN115934742A (en) * | 2022-12-26 | 2023-04-07 | 上海浦东发展银行股份有限公司 | Fault processing method, device, equipment and storage medium |
| CN116126832A (en) * | 2023-02-09 | 2023-05-16 | 平安付科技服务有限公司 | Database switching method, switching device, electronic equipment and storage medium |
| CN116107814A (en) * | 2023-04-04 | 2023-05-12 | 阿里云计算有限公司 | Database disaster recovery method, equipment, system and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116760693A (en) | 2023-09-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US5129080A (en) | Method and system increasing the operational availability of a system of computer programs operating in a distributed system of computers | |
| CN102916825A (en) | Management equipment of dual-computer hot standby system, management method and dual-computer hot standby system | |
| CN103684941A (en) | Arbitration server based cluster split-brain prevent method and device | |
| CN109474465A (en) | A kind of method and system of the high availability that can dynamically circulate based on server cluster | |
| CN110990200B (en) | Flow switching method and device based on multiple active data centers | |
| CN110333986B (en) | Method for guaranteeing availability of redis cluster | |
| CN108173971A (en) | A kind of MooseFS high availability methods and system based on active-standby switch | |
| CN111459639A (en) | Distributed task management platform and method supporting global multi-machine-room deployment | |
| CN110971662A (en) | Two-node high-availability implementation method and device based on Ceph | |
| CN110635941A (en) | Database node cluster fault migration method and device | |
| CN104794026B (en) | A kind of failover method of cluster instance multi-data source binding | |
| CN116185697B (en) | Container cluster management method, device and system, electronic equipment and storage medium | |
| CN112783694B (en) | Long-distance disaster recovery method for high-availability Redis | |
| CN116760693B (en) | Method and system for switching main and standby nodes of database | |
| CN114020279A (en) | Application software distributed deployment method, system, terminal and storage medium | |
| CN107181608B (en) | Method for recovering service and improving performance and operation and maintenance management system | |
| CN110716828B (en) | Database real-time backup method | |
| CN111460029A (en) | Data synchronization method and device | |
| CN104052799A (en) | Method for achieving high availability storage through resource rings | |
| CN110677288A (en) | Edge computing system and method generally used for multi-scene deployment | |
| CN114598711A (en) | Data migration method, device, equipment and medium | |
| CN114610545A (en) | Method, system, device and medium for reducing single point of failure of private cloud computing | |
| CN113890880A (en) | Method, system, equipment and storage medium for data synchronization among multiple nodes | |
| CN107888491A (en) | HSB standby systems and the AC double hot standby methods based on two layers of networking VRRP agreements | |
| CN110569303B (en) | MySQL application layer high-availability system and method suitable for various cloud environments |
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 |