CN111581284B - Database high availability method, device, system and storage medium - Google Patents

Database high availability method, device, system and storage medium Download PDF

Info

Publication number
CN111581284B
CN111581284B CN202010356546.6A CN202010356546A CN111581284B CN 111581284 B CN111581284 B CN 111581284B CN 202010356546 A CN202010356546 A CN 202010356546A CN 111581284 B CN111581284 B CN 111581284B
Authority
CN
China
Prior art keywords
node
slave
master
master node
cluster
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
CN202010356546.6A
Other languages
Chinese (zh)
Other versions
CN111581284A (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.)
Shanghai Zhongtongji Network Technology Co Ltd
Original Assignee
Shanghai Zhongtongji Network 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 Shanghai Zhongtongji Network Technology Co Ltd filed Critical Shanghai Zhongtongji Network Technology Co Ltd
Priority to CN202010356546.6A priority Critical patent/CN111581284B/en
Publication of CN111581284A publication Critical patent/CN111581284A/en
Application granted granted Critical
Publication of CN111581284B publication Critical patent/CN111581284B/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/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
    • 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/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/284—Relational databases
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]

Landscapes

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

Abstract

The invention relates to a database high availability method, a device, a system and a storage medium, wherein a master node and a slave node in a data center database form an MGR cluster, mySQL can automatically find a master library crash in an MGR mode, a new master node is generated by selecting a host system to provide read-write service for the outside, and automatic master-slave switching and fault recovery capability are realized; and the relationship between the nodes is maintained by combining the consul in the micro-service framework to realize the synchronization and the strong consistency of the data between the nodes, and the dynamic domain name server is combined to analyze the domain name of the switched main node to obtain the corresponding IP address, so that the reliability and the rapidness of automatic switching are ensured.

Description

Database high availability method, device, system and storage medium
Technical Field
The invention belongs to the technical field of database management, and particularly relates to a method, a device, a system and a storage medium for high availability of a database.
Background
The MYSQL database is the largest relational database of the current open source application, and a huge amount of applications store data in the MYSQL database. The security and reliability of stored data are the focus of the production database, and most of MYSQL databases solve single-point faults at present, and traditional MHA, PXC and other schemes are adopted, while the existing MHA (MHA is developed by the Japanese DenA company and is a set of excellent high-availability software which is used as the fault switching and master-slave promotion under the MySQL high-availability environment) can only be deployed in the same network section of the same machine room. For database machines of different network segments or the same network segments of different machine rooms, when the MHA switches the VIP (virtual IP), the problem that the application program can not find the host through the VIP connection is likely to occur, so that the data switching failure causes great loss for users.
Disclosure of Invention
In order to solve the problem that the switching failure is caused by the fact that a host cannot be found easily in the switching of a different-place machine room in the different-place disaster recovery prior art, the invention provides a database high-availability method, a database high-availability device, a database high-availability system and a database storage medium.
The technical scheme adopted by the invention is as follows:
a database high availability method, comprising:
determining master nodes and slave nodes of each data center database;
constructing an MGR cluster based on the master node and the slave node;
constructing a condul based on the MGR cluster, and registering the master node and the slave node on service discovery of the condul to monitor states of the master node and the slave node in the MGR cluster;
and after the condul discovers that the states of the master node and/or the slave node in the MGR cluster are changed, the DNS-based dynamic domain name service sends an IP address corresponding to the domain name of the new master node to the condul client.
Further, the monitoring the states of the master node and the slave node in the MGR cluster by using the service discovery of the condu specifically includes:
and carrying out data synchronization and relation maintenance based on gossip protocol in the susul and between the master node and the cluster nodes of the slave nodes in the MGR cluster.
Further, the monitoring the states of the master node and the slave node in the MGR cluster by using the service discovery of the condu specifically further includes:
and monitoring the node master-slave conversion state based on detection scripts preset on the master node and the slave node.
Further, communication is performed between different data centers based on the Internet.
Further, the operation mode of the MGR cluster is a single master two slave mode, and the single master two slave mode specifically is: and one master node drives two slave nodes to store data.
Further, the master node is responsible for the read-write function of the data center and synchronizes data with the slave node.
Further, at least two client services are included in the consul, each of the client services being configured to monitor a specified database.
According to an embodiment of the invention, a database high availability device comprises:
the MGR cluster module is used for determining a master node and a slave node of each data center database and constructing an MGR cluster based on the master node and the slave node;
a condul module, configured to construct condul based on the MGR cluster, and register the master node and the slave node to service discovery of the condul to monitor states of the master node and the slave node in the MGR cluster;
and the dynamic domain name module is used for sending the IP address corresponding to the domain name of the new master node to the client of the consul after the consul finds the master node and/or the slave node in the MGR cluster is changed.
A database high availability system according to an embodiment of the present invention includes a memory and a processor, the memory having stored therein a computer program which, when invoked by the processor for execution, implements a database high availability method as described above.
A storage medium according to an embodiment of the present invention has stored therein a computer program for performing at least the database high availability method as described above.
The beneficial effects of the invention are as follows: according to the method, a master node and a slave node in a data center database form an MGR cluster, a master library crash can be automatically found by MySQL in an MGR mode, a new master node is generated by selecting a master system to provide read-write service to the outside, and automatic master-slave switching and fault recovery capability are realized; and the relationship between the nodes is maintained by combining the consul in the micro-service framework to realize the synchronization and the strong consistency of the data between the nodes, and the dynamic domain name server is combined to analyze the domain name of the switched main node to obtain the corresponding IP address, so that the reliability and the rapidness of automatic switching are ensured.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a database high availability method provided in accordance with an exemplary embodiment;
FIG. 2 is a block diagram of a database high availability method provided in accordance with an exemplary embodiment;
FIG. 3 is a schematic diagram of a consul provided in accordance with an example embodiment;
fig. 4 is a schematic diagram of a condul provision service provided according to an exemplary embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. It will be apparent that the described embodiments are only some, but not all, embodiments of the invention. All other embodiments, based on the examples herein, which are within the scope of the invention as defined by the claims, will be within the scope of the invention as defined by the claims.
Referring to fig. 1 to 4, an embodiment of the present invention provides a database high availability method, including the steps of:
101. determining master nodes and slave nodes of each data center database;
102. constructing an MGR cluster based on the master node and the slave node;
103. constructing a consul based on the MGR cluster, and registering a master node and a slave node to the service discovery of the consul to monitor the states of the master node and the slave node in the MGR cluster;
104. the dynamic domain name service based on DNS sends the IP address corresponding to the domain name of the new master node to the client of the consul after the consul discovers that the states of the master node and/or the slave nodes in the MGR cluster are changed.
Specifically, mySQL Group Replication (MGR) is a solution of high availability and high expansion of MySQL, and is provided in a plug-in form, so that final consistency of distributed data is achieved, and the MGR has the following characteristics:
realizing group replication based on a distributed paxos protocol, and ensuring data consistency;
the automatic detection mechanism can continue to work as long as most nodes are not down, and a brain crack prevention protection mechanism is built in;
the addition and removal of the nodes can automatically update the group member information, and after the new node is added, incremental data is automatically synchronized from other nodes until the incremental data is consistent with the data of other nodes;
and providing a single main mode and a multi-main mode, wherein the single main mode can automatically select main after the main library is down, all writing is performed at a main node, and the multi-main mode supports multi-node writing. The principle is based on the replication group being a server cluster that interacts with each other through messaging. The communication layer provides guarantee mechanisms such as atomic message (atomic message) and complete ordered information interaction, so that multi-master updating based on a replication protocol is realized, automatic master-slave switching and fault recovery capability are realized, a single master mode is taken as an example, primary serves as a readable and writable node which is unique in externally providing read-write service by a master node, and other nodes can provide read service by slave nodes. In the traditional master-slave replication mode, if a master node generates crash, mySQLDBA needs to manually upgrade a slave library into a new master library, and after the old master library is restarted, the change master to is required to be executed for replication relation reconstruction, and start slave is executed for replication. In case of semi-sync copying, semi-sync parameter configuration is also required. But under the MGR mode, mySQL can automatically find the master library crash, and a new master node is generated through the master selection system to provide read-write service for the outside. After the old main node is restarted, the DBA can re-add the crash node into the Group only by executing the start group_reply, so that the operation and maintenance convenience and the system robustness are greatly improved.
The susl is a very important module in the micro-service architecture, provides functions of service registration, service discovery and the like, supports multiple data centers, and is interconnected through the Internet, meanwhile, note that only a Server node joins the communication across the data centers in order to improve the communication efficiency.
In a single data center, consul is divided into two nodes (all nodes are also called agents) of Client and Server, the Server node stores data, and the Client is responsible for health examination and forwarding data requests to the Server; the Server node has a loader and a plurality of Followers, the loader node synchronizes data to the Follower, and when the loader hangs up, an election mechanism is started to generate a new loader.
The susul nodes in the cluster maintain membership via gossip protocol, that is, a certain node knows which nodes are now in the cluster, whether they are clients or servers. The dialect protocols of a single data center use both TCP and UDP communications and both use 8301 ports. The streaming protocols across the data center also use both TCP and UDP communications, port usage 8302.
The read-write request of the data in the cluster can be directly sent to the Server, or can be forwarded to the Server by using RPC through Client, the request finally reaches the Leader node, and under the condition of slightly stale data, the read-write request can be completed in the common Server node, and the read-write and the copy of the data in the cluster are completed through the 8300 port of TCP.
In specific use, a condul program is arranged on the node, when the service discovery adopts a DNS form, the service discovery domain name of the node is directly used, so that the domain name resolution request reaches the DNS proxy of the client and is forwarded to the conducing device to further obtain the IP address of the corresponding port, and the micro-service client can quickly obtain the IP address so as to quickly obtain connection with the master node to ensure the smoothness of operation.
Therefore, by constructing the nodes of the data center into the MGR cluster, when the master node fails, the rapid master-slave switching can be realized, the data of the master node and the slave node can keep strong consistency through the consul service discovery, the dynamic Domain Name Service (DNS) modifies domain name information through scripts, and when the application is reconnected again, the domain name corresponds to a new address. The function of automatically and rapidly switching the master and slave is achieved, so that the high availability function of the database is achieved.
As a possible implementation manner of the above embodiment, taking a single master mode of MGR as an example, after MGR cluster is built, condul is built to register mysql-primary (database master node) and mysql-slave (database slave node) to service discovery:
wherein, condul-server: 192.168.202.177;
consul-client：192.168.202.174、192.168.202.175、192.168.202.176；
configuration files are respectively placed in the success-server and the success-client, and the success-client is: 192.168.202.174, 192.168.202.175, 192.168.202.176 are written with a detect primay script and a detect slave script as follows:
startup of the success service on 192.168.202.177, startup of the success client on 192.168.202.174, 192.168.202.175, 192.168.202.176; and finally, configuring a domain name server IP at the App end to analyze the domain name of the consul suffix, and analyzing and jumping the DNS.
In some embodiments of the present invention, taking a data center set in Huzhou as an example, a DNS server of a local data center queries an a record of a database, the DNS forwards a domain name resolution protocol to consul (hereinafter referred to as micro service), the micro service returns an IP address, a micro service client periodically checks the state of the database, and after a master node of an MGR cluster fails, the DNS server obtains the IP address of a new master node to achieve data strength consistency, thereby preventing data loss.
In another embodiment of the invention, data centers are respectively set up in Shanghai and Huzhou, and the two data centers are simultaneously configured with gossip protocol, and the data centers ensure data consistency through the protocol. If the central backbone network fails, data in Shanghai and Huzhou data centers are inconsistent, and two sides automatically synchronize difference data after the network is recovered, so that data consistency is realized. Each data center manages services under the center. If the Shanghai center crashes, the Huzhou center will take over all node services for a defined period of time for all applications to use. And recovering the Shanghai center, and incrementally synchronizing the data by adopting a plurality of rules which obey minority and snapshot new and old. The dynamic DNS domain name proxy service is responsible for resolving and maintaining all host A records of mysql.ztosys.com, and provides services to the outside in a service mode;
the dynamic DNS master node is responsible for the data center read-write function, the dynamic DNS slave node is responsible for communicating with the dynamic DNS agent, and when the agent reads and writes data, the slave node can forward the request to the dynamic DNS master node, and the master node is responsible for updating the data and synchronizing the data. The agent uploads the state of its own service every N seconds, and if the agent connection is not enabled, the dynamic DNS server will display an agent exception on the server, and the agent will attempt an automatic reconnection. Each agent may run multiple client services, each to monitor specific functions of a given remote database, such as operating status, connection count, CPU, IO utilization, etc. Each service has timeliness indicating the status of the service during that time.
The HA functionality of the database is enhanced by employing dynamic DNS services in conjunction with MGR functionality. And the dynamic DNS service function is added, so that an application program can find a database through the dynamic domain name. The MGR provides strong consistency of data, provides data guarantee for automatic switching of the database, and can enable the data center to recover to be normal within 10 to 20 seconds when faults occur, so that the speed is faster than that of the existing single solution.
The embodiment of the invention also provides a database high-availability device, which comprises:
the MGR cluster module is used for determining a master node and a slave node of each data center database and constructing an MGR cluster based on the master node and the slave node;
the consul module is used for constructing consul based on the MGR cluster and registering the master node and the slave node to the service discovery of consul so as to monitor the states of the master node and the slave node in the MGR cluster;
and the dynamic domain name module is used for sending the IP address corresponding to the domain name of the new master node to the client of the condul after the DNS-based dynamic domain name service discovers the state of the master node and/or the slave node in the MGR cluster.
The specific implementation manner of the database high availability device may be referred to the embodiments of the database high availability method described in the foregoing embodiments, which are not described herein.
The embodiment of the invention also provides a database high availability system, which comprises a memory and a processor, wherein the memory stores a computer program, and the computer program realizes the database high availability method in the embodiment when being called and executed by the processor.
In order to adapt to the database high availability device provided by the embodiment of the present invention, the embodiment of the present invention further provides a storage medium for use, where a computer program is stored, and the computer program is at least used to execute the database high availability method as described above.
The storage medium is for storing a computer program for performing at least the database high availability method of any of the above; the processor is configured to call and execute the computer program in the memory, and the storage medium is not limited to the floppy disk, the hard disk, and the flash disk, but may also use other memories, and the present invention is not limited herein.
The database high availability method provided by the embodiment of the invention adopts dynamic DNS service and MGR function to be used together, so that the HA function of the database is improved. By adding the dynamic DNS service function, an application program can find a database through a dynamic domain name, and the MGR provides data strong consistency and data guarantee for automatic switching of the database.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
The foregoing description includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of various embodiments are possible. Accordingly, the embodiments described herein are intended to embrace all such alterations, modifications and variations that fall within the scope of the appended claims. Furthermore, as used in the specification or claims, the term "comprising" is intended to be inclusive in a manner similar to the term "comprising" as "comprising" is interpreted when employed as a transitional word in a claim. Furthermore, any use of the term "or" in the specification of the claims is intended to mean "non-exclusive or".
The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (8)

1. A method of high availability of a database, comprising:
determining master nodes and slave nodes of each data center database;
constructing an MGR cluster based on the master node and the slave node;
constructing a condul based on the MGR cluster, and registering the master node and the slave node on service discovery of the condul to monitor states of the master node and the slave node in the MGR cluster;
the dynamic domain name service based on DNS sends an IP address corresponding to the domain name of a new master node to a client of the condul after the condul discovers that the states of the master node and/or the slave nodes in the MGR cluster are changed;
the monitoring the states of the master node and the slave node in the MGR cluster through the service discovery of the condul specifically includes:
performing data synchronization and relation maintenance based on gossip protocol in the susul and between the master node and the cluster nodes of the slave nodes in the MGR cluster;
the monitoring the states of the master node and the slave node in the MGR cluster through the service discovery of the condul specifically further includes:
and monitoring the node master-slave conversion state based on detection scripts preset on the master node and the slave node.
2. The database high availability method according to claim 1, wherein communication between different data centers is based on the internet.
3. The method for high availability of databases according to claim 1, wherein the operation mode of the MGR cluster is a single master two slave mode, and the single master two slave mode is specifically: and one master node drives two slave nodes to store data.
4. A method of high availability of databases as claimed in claim 3, wherein the master node is responsible for read-write functions of a data center and synchronizes data with the slave node.
5. The method of any of claims 1 to 4, wherein at least two client services are included in the condul, each of the client services being configured to monitor a specified database.
6. A database high availability apparatus, comprising:
the MGR cluster module is used for determining a master node and a slave node of each data center database and constructing an MGR cluster based on the master node and the slave node;
a condul module, configured to construct condul based on the MGR cluster, and register the master node and the slave node to service discovery of the condul to monitor states of the master node and the slave node in the MGR cluster;
the dynamic domain name module is used for sending an IP address corresponding to the domain name of the new master node to the client of the consul after the consul finds out the state of the master node and/or the slave node in the MGR cluster;
the monitoring the states of the master node and the slave node in the MGR cluster through the service discovery of the condul specifically includes:
performing data synchronization and relation maintenance based on gossip protocol in the susul and between the master node and the cluster nodes of the slave nodes in the MGR cluster;
the monitoring the states of the master node and the slave node in the MGR cluster through the service discovery of the condul specifically further includes:
and monitoring the node master-slave conversion state based on detection scripts preset on the master node and the slave node.
7. A database high availability system comprising a memory and a processor, the memory having stored therein a computer program which when invoked by the processor performs the database high availability method of any one of claims 1 to 5.
8. A storage medium, characterized in that the storage medium has stored therein a computer program for at least performing the database high availability method of any one of claims 1 to 5.
CN202010356546.6A 2020-04-29 2020-04-29 Database high availability method, device, system and storage medium Active CN111581284B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010356546.6A CN111581284B (en) 2020-04-29 2020-04-29 Database high availability method, device, system and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010356546.6A CN111581284B (en) 2020-04-29 2020-04-29 Database high availability method, device, system and storage medium

Publications (2)

Publication Number Publication Date
CN111581284A CN111581284A (en) 2020-08-25
CN111581284B true CN111581284B (en) 2023-09-15

Family

ID=72126235

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010356546.6A Active CN111581284B (en) 2020-04-29 2020-04-29 Database high availability method, device, system and storage medium

Country Status (1)

Country Link
CN (1) CN111581284B (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112468314B (en) * 2020-10-29 2022-11-04 贵州新致普惠信息技术有限公司 Method for realizing automatic deployment of log service based on service grid
CN112437166A (en) * 2020-10-30 2021-03-02 四川新网银行股份有限公司 Automatic switching method for MySQL database domain names
CN112286738B (en) * 2020-11-19 2024-01-26 政采云有限公司 Method, system, equipment and readable storage medium for accessing database
CN112506630A (en) * 2020-12-01 2021-03-16 国科晋云技术有限公司 Multi-domain service platform architecture
CN112507031B (en) * 2020-12-22 2023-06-06 四川新网银行股份有限公司 Database switching automatic reconnection method and readable storage medium
CN112612851B (en) * 2020-12-24 2024-03-08 南京三眼精灵信息技术有限公司 Multi-center data synchronization method and device
CN113704029A (en) * 2021-09-24 2021-11-26 携程旅游信息技术（上海）有限公司 Node availability management and control method, node, cluster, device and medium
CN114826892A (en) * 2022-04-28 2022-07-29 济南浪潮数据技术有限公司 Cluster node control method, device, equipment and medium
CN115499299A (en) * 2022-09-13 2022-12-20 航天信息股份有限公司 Cluster equipment monitoring method and device
CN115934428B (en) * 2023-01-10 2023-05-23 湖南三湘银行股份有限公司 Main disaster recovery and backup switching method and device of MYSQL database and electronic equipment
CN117112701B (en) * 2023-10-20 2024-01-19 武汉吧哒科技股份有限公司 Node switching method in distributed database, computer equipment and storage medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108599996A (en) * 2018-04-03 2018-09-28 武汉斗鱼网络科技有限公司 Fault handling method, device and the terminal of data-base cluster
CN110798499A (en) * 2018-08-03 2020-02-14 高新兴科技集团股份有限公司 Distributed service coordination system and method

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7996532B2 (en) * 2009-03-06 2011-08-09 Novell, Inc Cluster-free techniques for enabling a directory protocol-based domain name system (DNS) service for high availability

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108599996A (en) * 2018-04-03 2018-09-28 武汉斗鱼网络科技有限公司 Fault handling method, device and the terminal of data-base cluster
CN110798499A (en) * 2018-08-03 2020-02-14 高新兴科技集团股份有限公司 Distributed service coordination system and method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
刘波 ; 胡景光 ; 黄天天 ; .云环境MMM数据库集群双主多从架构模型构建.计算机与数字工程.2016,(04),全文. *

Also Published As

Publication number Publication date
CN111581284A (en) 2020-08-25

Similar Documents

Publication Publication Date Title
CN111581284B (en) Database high availability method, device, system and storage medium
CN106062717B (en) A kind of distributed storage dubbing system and method
US9507678B2 (en) Non-disruptive controller replacement in a cross-cluster redundancy configuration
JP6404907B2 (en) Efficient read replica
EP2648114B1 (en) Method, system, token conreoller and memory database for implementing distribute-type main memory database system
CN106534328B (en) Node connection method and distributed computing system
US20120079090A1 (en) Stateful subnet manager failover in a middleware machine environment
JP5548829B2 (en) Computer system, data management method, and data management program
CN105493474B (en) System and method for supporting partition level logging for synchronizing data in a distributed data grid
WO2015006371A2 (en) Replication of data between mirrored data sites
WO2008148319A1 (en) Image recovery method, storage equipment and network system
Dustdar et al. Dynamic replication and synchronization of web services for high availability in mobile ad-hoc networks
CN108512753B (en) Method and device for transmitting messages in cluster file system
CN112783694B (en) Long-distance disaster recovery method for high-availability Redis
US11681593B2 (en) Selecting a witness service when implementing a recovery plan
CN114785807A (en) Data processing method and device, electronic equipment and storage medium
WO2015196692A1 (en) Cloud computing system and processing method and apparatus for cloud computing system
US10305987B2 (en) Method to syncrhonize VSAN node status in VSAN cluster
CN113905054B (en) RDMA (remote direct memory access) -based Kudu cluster data synchronization method, device and system
US20210184938A1 (en) Computing device and methods for synchronizing networking information with a topology server
JP2023541069A (en) Active-active storage systems and their data processing methods
CN114500289A (en) Control plane recovery method, device, control node and storage medium
CN110266795A (en) One kind being based on Openstack platform courses method
CN112019601B (en) Two-node implementation method and system based on distributed storage Ceph
CN116112500B (en) NFS high availability system and method based on fault detection and routing strategy

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