WO2024103898A1

WO2024103898A1 - Database cluster management method and apparatus

Info

Publication number: WO2024103898A1
Application number: PCT/CN2023/115359
Authority: WO
Inventors: 高新刚
Original assignee: 京东科技信息技术有限公司
Priority date: 2022-11-14
Filing date: 2023-08-29
Publication date: 2024-05-23
Also published as: CN115964436A

Abstract

The present disclosure relates to the technical field of computers, and provides a database cluster management method and apparatus. A specific embodiment of the database cluster management method comprises: in response to a data write transaction, writing data to be written into a master database in a database cluster, and transmitting said data from the master database to a plurality of slave databases in the database cluster; according to a response message received by the master database, determining a response result of each slave database group in the database cluster, the response message being sent by a slave database which said data is successfully written into; and according to the response result of each slave database group in the database cluster, generating a reply message corresponding to the data write transaction. According to the embodiment, the efficiency of transaction processing can be improved, the influence of network jitter and database node failure on transaction processing can be avoided, a flexible disaster recovery service for data consistency can be provided, and the disaster recovery strategy can be dynamically adjusted.

Description

Database cluster management method and device

This application claims priority to Chinese Patent Application No. 202211421245.2, filed on November 14, 2022, entitled “A Method and Apparatus for Database Cluster Management”, and the contents disclosed in the above-mentioned Chinese patent application are hereby cited in their entirety as a part of this application.

Technical Field

The present disclosure relates to the field of computer technology, and in particular to a method and device for database cluster management.

Background technique

Different industries have different requirements for database data consistency disaster recovery services. The data consistency disaster recovery method currently commonly used in the database field is the master-slave replication method, which includes a master database and multiple slave databases. The master database is responsible for providing read and write access services to the outside world, and the slave databases synchronously replicate the operation logs of the master database to back up the data in the master database in real time.

In the process of implementing the present disclosure, the inventors found that there are at least the following problems in the prior art:

Network jitter or excessive slave database downtime will block the data synchronization process and the response message return process of the slave database, resulting in low data writing efficiency in the master database.

Summary of the invention

In view of this, the embodiments of the present disclosure provide a method and device for database cluster management, which can improve transaction processing efficiency, avoid the impact of network jitter and database node failure on transaction processing, provide flexible data consistency disaster recovery services, and dynamically adjust disaster recovery strategies.

To achieve the above objective, according to one aspect of an embodiment of the present disclosure, a method for managing a database cluster is provided, including:

In response to a data write transaction, the data to be written is written into a master database in the database cluster, and transmitted from the master database to a plurality of slave databases in the database cluster;

Determine the response results of each slave database group in the database cluster according to the response message received by the master database; the response message is sent by the slave database that successfully writes the data to be written;

A response message corresponding to the data write transaction is generated according to the response results of each slave database group in the database cluster.

According to one or more embodiments of the present disclosure, determining the response results of each slave database group in the database cluster according to the response message received by the master database includes:

According to the response message received by the master database, the number of response messages of the slave database group that sends the response message is updated; when the number of response messages of any slave database group in the database cluster meets the preset group response strategy, a group response message of any slave database group is generated, thereby obtaining the response result of any slave database group.

According to one or more embodiments of the present disclosure, the method further includes:

Before determining the response results of each slave database group in the database cluster, the slave database group configuration information of the database cluster is obtained, and the slave database group configuration information includes: slave databases included in each slave data group in the database cluster, and their group response strategies.

According to one or more embodiments of the present disclosure, the response result is: generating a group response message or not generating a group response message; generating a reply message corresponding to the data write transaction according to the response results of each slave database group in the database cluster, including:

Determine whether the number of group response messages in the database cluster meets the preset wake-up response strategy; if so, generate a wake-up response message corresponding to the data write transaction to indicate that the data to be written is successfully written to the database cluster; otherwise, generate an exception response message corresponding to the data write transaction to indicate that the data to be written is not successfully written to the database cluster.

Before generating a response message corresponding to the data write transaction, the wake-up response strategy configuration information of the database cluster is obtained, and the wake-up response strategy configuration information includes: the wake-up response strategy of the database cluster.

Before determining the response results of each slave database group in the database cluster, scanning the data replication mode configuration information of the database cluster to confirm that the group response strategy is in an enabled state;

When the group response strategy is in a closed state, a response message corresponding to the data write transaction is generated according to a preset response strategy and a response message received by the primary database.

According to a second aspect of an embodiment of the present disclosure, a database cluster management device is provided, including:

A data writing and transmission module, used for writing the data to be written into a master database in the database cluster in response to a data writing transaction, and transmitting the data from the master database to a plurality of slave databases in the database cluster;

A response result determination module, used to determine the response results of each slave database group in the database cluster according to the response message received by the master database; the response message is sent by the slave database that successfully writes the data to be written;

The response message generating module is used to generate a response message corresponding to the data writing transaction according to the response results of each slave database group in the database cluster.

According to one or more embodiments of the present disclosure, the device also includes: a group configuration information acquisition module, which is used to obtain the slave database group configuration information of the database cluster before determining the response results of each slave database group in the database cluster, and the slave database group configuration information includes: the slave databases contained in each slave data group in the database cluster, and their group response strategies.

According to one or more embodiments of the present disclosure, the device also includes: a wake-up response strategy configuration information acquisition module, which is used to obtain the wake-up response strategy configuration information of the database cluster before generating a response message corresponding to the data write transaction, and the wake-up response strategy configuration information includes: the wake-up response strategy of the database cluster.

According to one or more embodiments of the present disclosure, the apparatus further includes: a data replication mode configuration information scanning module, configured to scan the data replication mode configuration information of the database cluster before determining the response result of each slave database group in the database cluster to confirm that the group response strategy is in an on state;

According to a third aspect of an embodiment of the present disclosure, a database cluster system is provided, including:

A master database, a plurality of slave databases, and a database cluster management device configured on the master database;

The database cluster management device writes the data to be written into a master database in the database cluster in response to the data writing transaction, and transmits the data from the master database to multiple slave databases in the database cluster;

The database cluster management device determines the response results of each slave database group in the database cluster according to the response message received by the master database; the response message is sent by the slave database that successfully writes the data to be written;

The database cluster management device generates a response message corresponding to the data write transaction according to the response results of each slave database group in the database cluster.

According to a fourth aspect of an embodiment of the present disclosure, there is provided an electronic device, including:

one or more processors;

a storage device for storing one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any one of the above embodiments.

According to a fifth aspect of an embodiment of the present disclosure, a computer-readable medium is provided, on which a computer program is stored, and when the program is executed by a processor, the method described in any of the above embodiments is implemented.

An embodiment of the above invention has the following advantages or beneficial effects: by grouping the slave databases and generating a reply message according to the response result of the slave database group, the influence of the slave database node failure and network jitter on the master database receiving the response message can be avoided, and the processing efficiency of the database write service can be improved; by configuring the database group configuration information, different slave databases and group response strategies can be obtained, so as to meet different data consistency disaster recovery strategies; by configuring the wake-up response strategy configuration information of the database cluster, the wake-up response strategy of the database cluster can be flexibly adjusted to further improve the transaction processing efficiency of the database cluster; by scanning the data replication mode configuration information of the database cluster, the latest data replication mode can be obtained and made effective, and by modifying the data replication mode configuration information, the Adjust the database's data consistency disaster recovery strategy without restarting the database cluster service.

The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with specific implementation examples.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are used to better understand the present disclosure and do not constitute an improper limitation on the present disclosure.

FIG1 is a schematic diagram of the main process of a method for managing a database cluster according to an embodiment of the present disclosure;

FIG2 is a schematic diagram of a process of database cluster management according to an embodiment of the present disclosure;

FIG3 is a schematic diagram of a single group working principle of a method for managing a database cluster according to a reference embodiment of the present disclosure;

FIG4 is a schematic diagram of grouping slave databases according to different disaster recovery requirements;

FIG5 is a schematic diagram of the overall working principle of a method for managing a database cluster according to another reference embodiment of the present disclosure;

FIG6 is a schematic diagram of a process of database cluster management summarized according to the prior art;

FIG7 is a schematic diagram of main modules of a device for database cluster management according to an embodiment of the present disclosure;

FIG8 is a schematic diagram of a database cluster system according to an embodiment of the present disclosure;

FIG9 is a diagram of an exemplary system architecture in which embodiments of the present disclosure may be applied;

FIG. 10 is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present disclosure.

Detailed ways

The following is a description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

It should be noted that, in the absence of conflict, the embodiments of the present disclosure and the features therein may be combined with each other; in the technical solution of the present disclosure, the acquisition, storage and application of user personal information involved all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

Database-related products and technologies have been widely used in many industries such as finance, transportation, medical care, and education, becoming the cornerstone products of digital construction. Database failures are inevitable, so the data consistency disaster recovery capability of database products is a core issue of concern to users. At present, the disaster recovery method commonly used by database products is the master-slave replication method. The master database is responsible for providing services to the outside world, and the slave database will synchronize the operations of the master database and back up the data in the master database in real time. When the master database fails, a slave database is selected as the new master database to continue to provide database services.

However, the disaster recovery strategy of the master-slave replication method is single and cannot meet the personalized needs of users in different industries for data consistency disaster recovery strategies; when adjusting the disaster recovery strategy, the database cluster service needs to be restarted, affecting business continuity; and network jitter and slave database failures will also affect the data synchronization of the master database, resulting in low transaction processing efficiency.

In view of this, according to one aspect of an embodiment of the present disclosure, a method for managing a database cluster is provided.

Fig. 1 is a schematic diagram of the main process of the method for managing a database cluster according to an embodiment of the present disclosure. As shown in Fig. 1 , the method for managing a database cluster according to an embodiment of the present disclosure mainly includes the following steps S101 to S103.

Step S101 , in response to a data writing transaction, write the data to be written into a master database in a database cluster, and transmit the data from the master database to a plurality of slave databases in the database cluster.

In the embodiment of the present disclosure, data write transactions usually come from transaction requests issued by various applications on the computer, and the transaction requests are received by the database cluster. The database cluster includes a The master database of the database cluster is responsible for providing external read and write access services, and the slave database of the database cluster is responsible for real-time synchronization of the operation log in the master database, so that the data in the slave database is consistent with that in the master database, so as to serve as a backup of the master database. In the data replication process, a master database and multiple slave databases are used to obtain a sufficient number of data backups to ensure that when the master database fails, there is a slave database with complete data backup, and it also prepares for providing multiple data consistency disaster recovery strategies.

FIG. 2 is a flow chart of database cluster management according to an embodiment of the present disclosure. As shown in FIG. 2 , the database cluster includes a master database 202 and multiple slave databases, wherein the slave database 205 is marked as an example. First, various applications 201 on the computer send data write requests to the master database 202 in the database cluster, and the master database writes the corresponding transaction operation to the binary log 203. By monitoring the relevant log parameters of the master database 202, it can be identified that the data of the master database 202 and the multiple slave databases are inconsistent, and then the multiple slave databases will send a communication request to the master database 202 to read the newly added log information on the master database. Taking the slave database 205 as an example, the slave database 205 saves the received log information to the relay log 204, and subsequently transmits the data to be written from the master database 202 to the slave database 205 according to the log information, and writes the transaction operation of the slave database 205 to the binary log 206.

Step S102, determining the response results of each slave database group in the database cluster according to the response message received by the master database; the response message is sent by the slave database that has successfully written the data to be written.

After the data to be written is successfully written to the slave database, the slave database will send a corresponding response message to the master database to indicate that the slave database has completed the data writing operation. The content of the response message received by the master database includes: the slave database number, the name of the log file read on the master database and the specific reading position in the log, the timestamp of receiving the response message, etc.

Slave database grouping is to group slave databases in the database cluster according to the preset group response strategy. The group response strategy can be determined according to the disaster recovery requirements that meet security regulations or the disaster recovery requirements set by the user. The response information received by the master database can determine the slave database that sends the response message, and then determine the slave database group to which the slave database belongs, and divide the response message into each slave database group, so as to determine the response result of each slave database group in the database cluster. By grouping the slave databases, the slave databases with unstable network or prone to downtime can be grouped with the slave databases with stable network, and the response message is generated according to the response result of the slave database group, which can avoid the influence of slave database node failure and network jitter on the master database receiving the response message, and improve the processing efficiency of the database write service.

According to a reference embodiment of the present disclosure, determining the response results of each slave database group in the database cluster according to the response message received by the master database includes:

According to the response message received by the main database, the number of response messages of the slave database group that sends the response message is updated; when the number of response messages of any slave database group in the database cluster meets the group response strategy, a group response message of any slave database group is generated to obtain the response result of any slave database group.

According to the content of the received response message, the slave database that sends the response message can be determined, and the slave database group to which the slave database is located can be determined according to the slave database, and then the slave database group to which the response message belongs can be determined. By recording the number of response messages of the slave database group, the completion of the data write transaction of the slave database in each slave database group can be known. Each slave database group has a corresponding group response strategy, and whether the group response strategy is met is determined according to the response message of the slave database group. When the slave database meets its corresponding group response strategy, a group response message of the slave database group will be generated. By using the slave database group and the group response strategy, it is possible to avoid waiting for a long time for a slave database in an unstable network to return a response message, and to avoid the problem that a slave database failure cannot return a response message and it is difficult to determine the response result, thereby improving the transaction processing efficiency of the database cluster.

As shown in Figure 2, after the response message sent by the slave database is received by the master database, First, determine the slave database group to which the response message belongs based on the slave database. For example, slave database 205 belongs to slave database group 1. Then, based on the response message sent by slave database 205 to the main database, the number of response messages of slave database group 1 should be increased; the group response strategy can be to set a response message number threshold. When the number of response messages of the slave database group satisfies the group response strategy, that is, the number of response messages of the slave database group reaches the response message number threshold, the response result of the slave database group is obtained.

FIG3 is a schematic diagram of the working principle of a single group of a method for database cluster management according to a reference embodiment of the present disclosure. As shown in FIG3, it is a state change process of a slave database group, and the group response strategy of the slave database group is: when the response message of the slave database group is 2, a group response message of the slave database group is generated. The slave database group has two states. In the slave database group state 301, the main database receives a response message from the group member 1 of the slave database group. At this time, the number of response messages of the slave database group is 1, and the group response strategy of the slave database group is not met, so the group response message of the slave database group cannot be generated; after a period of waiting for the response message, the main database receives a response message from the group member 2 of the slave database group, so the slave database group state 301 changes to the slave database group state 302. In the slave database group state 302, the number of response messages of the slave database group is 2 at this time, which meets the group response strategy of the slave database group, that is, the number of response messages reaches the response message number threshold, so the slave database group will generate a group response message of the slave database group, and then obtain the response result of the slave database group.

According to another reference embodiment of the present disclosure, before determining the response results of each slave database group in the database cluster, the slave database group configuration information of the database cluster can be obtained. The slave database group configuration information includes: the slave databases contained in each slave data group in the database cluster, and their group response strategies.

The database cluster has slave database group configuration information, which is obtained based on the user's disaster recovery requirements, including: slave databases contained in each slave data group in the database cluster, and their group response strategies. When grouping the database, you can group them according to the data security regulations of different industries, or you can group the slave databases according to the personalized disaster recovery needs of users. Through the slave database group configuration information, you can obtain the latest slave database grouping and group response strategy to meet the latest disaster recovery needs and avoid the new slave database grouping and group response strategy not taking effect in time. And by configuring the slave database group configuration information, you can flexibly group the slave databases, and implement different group response strategies for different slave database groups, thereby meeting the disaster recovery needs of different users and improving the transaction processing efficiency of the database cluster.

FIG4 is a schematic diagram of grouping slave databases according to different disaster recovery requirements. As shown in FIG4, the slave databases in the three computer rooms in the two cities (i.e., two locations and three centers) are grouped, and the corresponding slave database grouping configuration information is obtained according to different disaster recovery requirements, so that different slave database groups can be obtained. Exemplarily, in slave database group 401, each computer room has a slave database, and the disaster recovery requirement is that the data replication of at least one slave database is consistent, then all slave databases can be grouped together, and when the master database receives a response message, it means that at least one slave database has successfully completed data replication, and the disaster recovery requirement of slave database group 401 can be met; in slave database group 402, each computer room has a slave database, and the disaster recovery requirement is that the data replication of any remote computer room is consistent, and the remote computer room refers to other computer rooms other than the computer room where the master database is located, namely computer room B and computer room C. According to the above grouping strategy, the slave databases in computer room B and computer room C can be grouped together, and computer room A where the master database is located can be grouped together separately. When the master database receives a group response message from the slave database group where computer rooms B and computer room C are located, , indicating that any slave database in a remote computer room has successfully completed data replication, that is, the disaster recovery requirement of slave database group 402 is met; in slave database group 403, the disaster recovery requirement is that the remote data replication is consistent, then the slave databases in computer room C that are not in the same city as the master database can be grouped together, and when the master database receives the group response message of the slave database group in other cities, it indicates that the remote slave databases have successfully completed data replication, that is, the disaster recovery requirement of slave database group 403 is met; in slave database group 404, the disaster recovery requirement is that the data replication of the three computer rooms is consistent, then the slave databases in different computer rooms can be grouped together respectively, and when the master database receives the group response message of different slave database groups, it indicates that the slave databases in different computer rooms have successfully completed data replication, that is, the disaster recovery requirement of slave database group 404 is met.

As shown in Figure 4, according to the slave database grouping configuration information of the database cluster, it is possible to obtain which slave databases are included in each slave database group and the preset grouping response strategy; and according to the user's disaster recovery needs, the slave database grouping configuration information is adjusted to obtain different slave database groups and different grouping response strategies. The slave database grouping method is very flexible and can fully consider the situation of multiple regions and multiple computer rooms. The number of slave database groups can be one or more, and the number of slave databases in a slave database group can be one or more.

Step S103: Generate a response message corresponding to the data write transaction according to the response results of each slave database group in the database cluster.

Each slave database group has a response result, and different response messages corresponding to the data write transaction can be generated according to different response results. Figure 5 is a schematic diagram of the overall working principle of the method for database cluster management according to another reference embodiment of the present disclosure. As shown in Figure 5, each slave database group will generate a group response message to indicate the response result, and the group response messages of each slave database group can be collected together for easy analysis and processing. According to the response result indicated by the group response message, a response message corresponding to the data write transaction is generated. By generating a response message based on the response result, the response strategy can be flexibly set to meet various disaster recovery requirements and improve the transaction processing efficiency of the database cluster.

According to a reference embodiment of the present disclosure, the response result is: generating a group response message or not generating a group response message; generating a reply message corresponding to the data write transaction according to the response results of each slave database group in the database cluster, including:

The response results can be divided into generating a group response message and not generating a group response message. When the number of response messages from the database group does not meet the group response strategy, the database group will issue a response result of not generating a group response message; when the number of response messages from the database group meets the group response strategy, the database group will issue a response result of generating a group response message. The database cluster is preset with a wake-up response strategy, as shown in Figure 5. The group response messages are aggregated through the group response message set to determine whether the number of group response messages meets the preset wake-up response strategy. If the wake-up response strategy is met, a wake-up response message is issued. If the wake-up response strategy is not met, an abnormal response message is issued. Through the response result, the response status of each group can be clearly known. Setting the wake-up response strategy can meet different disaster recovery requirements. Setting different response messages can understand the data writing status of the data to be written. Even if the wake-up response strategy is not met, corresponding processing can be made according to the abnormal response message, thereby further improving the transaction processing efficiency of the database cluster.

According to another reference embodiment of the present disclosure, before generating a response message corresponding to a data write transaction, wake-up response strategy configuration information of a database cluster is obtained, and the wake-up response strategy configuration information includes: a wake-up response strategy of the database cluster.

The database cluster has wake-up response strategy configuration information, including the wake-up response strategy of the database cluster. Specifically, the wake-up response strategy may be related to the reply message. Exemplarily, a reply message number threshold is set in the wake-up response strategy. When the number of reply messages reaches the reply message number threshold, it is judged that the wake-up response strategy is satisfied; otherwise, when the number of reply messages reaches the reply message number threshold, it is judged that the wake-up response strategy is not satisfied. By obtaining the wake-up response strategy configuration information, the latest wake-up response strategy can be obtained to meet the latest disaster recovery requirements and avoid the new wake-up response strategy not taking effect in time.

FIG6 is a schematic diagram of the process of database cluster management summarized according to the prior art. As shown in FIG6, when the slave database completes the data write transaction and returns the response message, each slave database will return its own response message to the master database, and the database cluster will set a response message number threshold, which is usually greater than the value of the slave database. The wake-up response message is generated only when the number of response messages returned by the slave databases received by the master database reaches the threshold of the number of response messages. For example, there are 10 slave databases in the database cluster. According to the response strategy of the prior art, the master database needs to receive at least 6 response messages sent by the slave databases before sending a wake-up response message; and according to the technical solution of the embodiment of the present disclosure, the 10 slave databases can be divided into two slave database groups according to the slave database group configuration information, each slave database group has 5 slave databases, and the group response strategy is set to generate a group response message of the slave database group when the number of response messages of the slave database group is 1; because there are two slave database groups, the wake-up response strategy configuration information is set, and the wake-up response strategy is set to generate a wake-up response message corresponding to the data write transaction when two group response messages are obtained, otherwise an abnormal response message is generated. Under the above-mentioned group response strategy, the master database only needs to wait for the response messages of two slave databases to generate two group response messages, thereby obtaining the wake-up response message corresponding to the data write transaction. Since the slave database group configuration information can be flexibly configured, all slave databases can even be divided into one slave database group, so that the master database only needs to wait for the response message of one slave database to obtain the wake-up response message corresponding to the data write transaction. Compared with the prior art, the number of response messages waited by the technical solution of the embodiment of the present disclosure is much smaller than the number of response messages waited in the prior art, so it can greatly improve the transaction processing efficiency while meeting the disaster recovery requirements.

As another example, in a database cluster architecture with multiple computer rooms in multiple regions, using existing technologies to wait for response messages from a slave database is often affected by network jitter, and the response efficiency of a slave database that is not in the same region as the master database is very low. According to the technical solution of the embodiment of the present disclosure, slave databases in the same region (i.e., local) as the master database and slave databases in other different regions (i.e., remote) can be divided into a slave database group, and the group response strategy of the slave database group can be set as follows: when the number of response messages from the slave database group is a value X, a group response message of the slave database group is generated, where the value X is a value not greater than the number of local slave databases. In this way, a group response message and a wake-up reply message can be generated when a response message is returned from a local slave database, thereby avoiding long waits for group response messages from remote slave database groups, and avoiding the impact of network jitter or failure of a slave database on the generation of group response messages and wake-up reply messages, thereby improving the number of responses. Transaction processing efficiency of database clusters.

According to another referenceable embodiment of the present disclosure, before determining the response results of each slave database group in the database cluster, scan the data replication mode configuration information of the database cluster to confirm that the group response strategy is in the enabled state;

The database cluster has data replication mode configuration information, and the data replication mode of the slave database can be configured according to the data replication mode configuration information. When the group response strategy is in the on state, the data replication mode set in the data replication mode configuration information is used; when the group response strategy is in the off state, the default data replication mode is used. Specifically, a system table can be set in the master database to save the data replication mode configuration information in the system table. The data replication mode configuration information may include: the number of the group response strategy, that is, multiple group response strategies can be saved in the system table; the name of the group response strategy; the specific group response strategy, which can be a string, by setting the string matching mode, different group response strategies are matched according to different strings obtained from the system table; the default group response strategy; the creator, modifier and corresponding timestamp of each group response strategy, etc.

Through the data replication mode configuration information, the default data replication mode can be set, and the consistency of data replication can still be guaranteed when the group response strategy is not enabled. And by scanning the data replication mode configuration information of the database cluster, the latest data replication mode can be obtained, including: how to group from the database, the group response strategy of each group, and the wake-up response strategy. By modifying the specific content in the system table, the data consistency disaster recovery strategy of the database can be adjusted in real time without restarting the database cluster service.

According to a second aspect of an embodiment of the present disclosure, a device for managing a database cluster is provided.

FIG. 7 is a schematic diagram of main modules of a device for managing a database cluster according to an embodiment of the present disclosure. As shown in FIG. 7 , the device 700 for managing a database cluster mainly includes:

The data writing and transmission module 701 is used to write the data to be written into the master database in the database cluster in response to the data writing transaction, and transmit the data from the master database to multiple slave databases in the database cluster;

A response result determination module 702 is used to determine the response results of each slave database group in the database cluster according to the response message received by the master database; the response message is sent by the slave database that successfully writes the data to be written;

The response message generating module 703 is used to generate a response message corresponding to the data writing transaction according to the response results of each slave database group in the database cluster.

According to the response message received by the main database, the number of response messages of the slave database group that sends the response message is updated; when the number of response messages of any slave database group in the database cluster meets the preset group response strategy, a group response message of any slave database group is generated, thereby obtaining the response result of any slave database group.

According to a reference embodiment of the present disclosure, the device 700 for managing a database cluster also includes: a group configuration information acquisition module, which is used to obtain the slave database group configuration information of the database cluster before determining the response results of each slave database group in the database cluster, and the slave database group configuration information includes: the slave databases contained in each slave data group in the database cluster, and their group response strategies.

According to another referenceable embodiment of the present disclosure, the response result is: generating a group response message or not generating a group response message; generating a reply message corresponding to the data write transaction according to the response results of each slave database group in the database cluster, including:

Determine whether the number of group response messages in the database cluster meets the preset wake-up response strategy; if so, generate a wake-up response message corresponding to the data write transaction to indicate that the data to be written is successfully written to the database cluster; otherwise, generate an exception corresponding to the data write transaction A response message indicating that the data to be written was not successfully written to the database cluster.

According to another reference embodiment of the present disclosure, the device 700 for database cluster management also includes: a wake-up response strategy configuration information acquisition module, which is used to obtain the wake-up response strategy configuration information of the database cluster before generating a response message corresponding to the data write transaction, and the wake-up response strategy configuration information includes: the wake-up response strategy of the database cluster.

According to another referenceable embodiment of the present disclosure, the database cluster management apparatus 700 further includes: a data replication mode configuration information scanning module, which is used to scan the data replication mode configuration information of the database cluster before determining the response result of each slave database group in the database cluster to confirm that the group response strategy is in an on state;

When the group response strategy is in the closed state, a response message corresponding to the data write transaction is generated according to the preset response strategy and the response message received by the primary database.

It should be noted that the specific implementation content of the device for managing a database cluster described in the embodiment of the present disclosure has been described in detail in the method for managing a database cluster described above, so the repeated content will not be described here.

According to a third aspect of an embodiment of the present disclosure, a database cluster system is provided.

FIG8 is a schematic diagram of a database cluster system according to an embodiment of the present disclosure. As shown in FIG8 , the database cluster system 800 mainly includes: a master database 801, multiple slave databases, and a database cluster management device 802 configured on the master database 801, wherein the multiple slave databases can be distributed in different computer rooms in different cities, and the database cluster management device 802 can manage the slave databases in the database cluster system 800 across computer rooms and regions;

The database cluster management device 802 configured on the master database 801 writes the data to be written into the master database 801 in the database cluster in response to the data writing transaction, and transmits the data from the master database 801 to the multiple slave databases in the database cluster;

The database cluster management device 802 configured on the master database 801 determines the response of each slave database group in the database cluster according to the response message received by the master database 801. Result; A response message is sent from the slave database that successfully writes the data to be written;

The database cluster management device 802 configured on the master database 801 generates a response message corresponding to the data write transaction according to the response results of each slave database group in the database cluster.

It should be noted that the specific implementation content of the database cluster system 800 described in the embodiment of the present disclosure has been described in detail in the method and device for database cluster management described above, so the repeated content will not be described here. The relevant content of the device 802 for database cluster management configured on the main database 801 can be found in the introduction of the second aspect of the embodiment of the present disclosure, and will not be repeated here.

According to the technical solution of the embodiment of the present disclosure, by grouping the slave databases and generating a reply message according to the response result of the slave database group, the influence of the slave database node failure and network jitter on the reception of the response message of the master database can be avoided, thereby improving the processing efficiency of the database write service; by configuring the database group configuration information, different slave databases and group response strategies can be obtained to meet different data consistency disaster recovery strategies; by configuring the wake-up response strategy configuration information of the database cluster, the wake-up response strategy of the database cluster can be flexibly adjusted to further improve the transaction processing efficiency of the database cluster; by scanning the data replication mode configuration information of the database cluster, the latest data replication mode can be obtained and made effective, and by modifying the data replication mode configuration information, the data consistency disaster recovery strategy of the database can be adjusted in real time without restarting the database cluster service.

According to a fourth aspect of an embodiment of the present disclosure, there is provided an electronic device for database cluster management, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method provided by the first aspect of the embodiment of the present disclosure.

According to a fifth aspect of an embodiment of the present disclosure, a computer-readable medium is provided, on which a computer program is stored, and when the program is executed by a processor, the method provided by the first aspect of the embodiment of the present disclosure is implemented.

FIG. 9 shows an exemplary system architecture 900 to which the method or apparatus for managing a database cluster according to an embodiment of the present disclosure can be applied.

As shown in Fig. 9, system architecture 900 may include terminal devices 901, 902, 903, a network 904, and a server 905. Network 904 is used to provide a medium for communication links between terminal devices 901, 902, 903 and server 905. Network 904 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

Users can use terminal devices 901, 902, 903 to interact with server 905 through network 904 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 901, 902, 903, such as database cluster management applications, database cluster status display applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

The terminal devices 901 , 902 , and 903 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers, etc.

The server 905 may be a server that provides various services, such as a background management server (only as an example) that provides support for data write requests sent from upstream terminal devices 901, 902, and 903. In response to the data write transaction, the background management server may write the data to be written into the master database in the database cluster, and transmit the data from the master database to multiple slave databases in the database cluster; determine the response results of each slave database group in the database cluster according to the response message received by the master database; the response message is sent by the slave database that successfully writes the data to be written; generate a response message corresponding to the data write transaction according to the response results of each slave database group in the database cluster; and feed back the response result of the data write transaction (only as an example) to the terminal device.

It should be noted that the method for billing management provided in the embodiment of the present disclosure is generally The method for managing a database cluster provided in the embodiment of the present disclosure may also be performed by the terminal devices 901, 902, and 903, and the apparatus for managing a database cluster may be provided in the terminal devices 901, 902, and 903 accordingly.

It should be understood that the number of terminal devices, networks and servers in Figure 9 is only for illustration purposes and any number of terminal devices, networks and servers may be provided as required.

Referring to Figure 10, a schematic diagram of the structure of a computer system 1000 suitable for implementing a terminal device of an embodiment of the present disclosure is shown. The terminal device shown in Figure 10 is only an example and should not limit the functions and scope of use of the embodiment of the present disclosure.

As shown in FIG. 10 , the computer system 1000 includes a central processing unit (CPU) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage part 1008 into a random access memory (RAM) 1003. In the RAM 1003, various programs and data required for the operation of the system 1000 are also stored. The CPU 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input/output (I/O) interface 1005 is also connected to the bus 1004.

The following components are connected to the I/O interface 1005: an input section 1006 including a keyboard, a mouse, etc.; an output section 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN card, a modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I/O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that a computer program read therefrom is installed into the storage section 1008 as needed.

In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program The computer program includes a computer program carried on a computer readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1009, and/or installed from the removable medium 1011. When the computer program is executed by the central processing unit (CPU) 1001, the above functions defined in the system of the embodiment of the present disclosure are executed.

It should be noted that the computer-readable medium shown in the embodiment of the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the embodiment of the present disclosure, the computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, device or device. In the embodiment of the present disclosure, the computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

The flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer programs according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram may represent a module, program segment, or a portion of the code. Part, the above-mentioned module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed basically in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of boxes in the block diagram or flow chart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

The modules involved in the embodiments described in the present disclosure may be implemented by software or by hardware. The modules described may also be set in a processor, for example, it may be described as: a processor includes a data writing and transmission module, a response result determination module and a reply message generation module, wherein the names of these modules do not constitute a limitation on the modules themselves under certain circumstances, for example, the response result determination module may also be described as "a module for determining a response result according to a response message returned from a database".

As another aspect, the disclosed embodiment also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device implements the following method: in response to a data write transaction, the data to be written is written to a master database in a database cluster, and the master database is transmitted to multiple slave databases in the database cluster; according to the response message received by the master database, the response result of each slave database group in the database cluster is determined; the response message is sent by the slave database that successfully writes the data to be written; according to the response result of each slave database group in the database cluster, a reply message corresponding to the data write transaction is generated.

According to the technical solution of the embodiment of the present disclosure, by grouping the slave databases and generating a reply message according to the response results of the slave database groups, the influence of slave database node failures and network jitter on the master database receiving the response message can be avoided, thereby improving the database write service efficiency. By configuring the database grouping configuration information, different slave databases and grouping response strategies can be obtained to meet different data consistency disaster recovery strategies; by configuring the database cluster wake-up response strategy configuration information, the database cluster wake-up response strategy can be flexibly adjusted to further improve the transaction processing efficiency of the database cluster; by scanning the database cluster data replication mode configuration information, the latest data replication mode can be obtained and made effective; by modifying the data replication mode configuration information, the database data consistency disaster recovery strategy can be adjusted in real time without restarting the database cluster service.

The above specific implementations do not constitute a limitation on the protection scope of the embodiments of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the embodiments of the present disclosure shall be included in the protection scope of the embodiments of the present disclosure.

Claims

A method for managing a database cluster, comprising:

In response to a data write transaction, the data to be written is written into a master database in the database cluster, and transmitted from the master database to a plurality of slave databases in the database cluster;

Determine the response results of each slave database group in the database cluster according to the response message received by the master database; the response message is sent by the slave database that successfully writes the data to be written;

A response message corresponding to the data write transaction is generated according to the response results of each slave database group in the database cluster.
The method according to claim 1, wherein determining the response results of each slave database group in the database cluster according to the response message received by the master database comprises:

According to the response message received by the master database, the number of response messages of the slave database group that sends the response message is updated; when the number of response messages of any slave database group in the database cluster meets the preset group response strategy, a group response message of any slave database group is generated, thereby obtaining the response result of any slave database group.
The method according to claim 2, wherein the method further comprises:

Before determining the response results of each slave database group in the database cluster, slave database group configuration information of the database cluster is obtained, and the slave database group configuration information includes: slave databases included in each slave data group in the database cluster, and their group response strategies.
The method according to claim 1, wherein the response result is: generating a group response message or not generating a group response message; generating a reply message corresponding to the data write transaction according to the response results of each slave database group in the database cluster, comprising:

Determine whether the number of group response messages in the database cluster meets the preset wake-up response strategy; if so, generate a wake-up response message corresponding to the data write transaction to indicate that the data to be written is successfully written to the database cluster; otherwise, generate an exception response message corresponding to the data write transaction to indicate that the data to be written is not successfully written to the database cluster.
The method according to claim 4, wherein the method further comprises:

Before generating a response message corresponding to the data write transaction, the wake-up response strategy configuration information of the database cluster is obtained, and the wake-up response strategy configuration information includes: the wake-up response strategy of the database cluster.
The method according to claim 1, wherein the method further comprises:

Before determining the response results of each slave database group in the database cluster, scanning the data replication mode configuration information of the database cluster to confirm that the group response strategy is in an enabled state;

When the group response strategy is in a closed state, a response message corresponding to the data write transaction is generated according to a preset response strategy and a response message received by the primary database.
A database cluster management device, comprising:

A data writing and transmission module, used for writing the data to be written into a master database in the database cluster in response to a data writing transaction, and transmitting the data from the master database to a plurality of slave databases in the database cluster;

A response result determination module, used to determine the response results of each slave database group in the database cluster according to the response message received by the master database; the response message is sent by the slave database that successfully writes the data to be written;

The response message generating module is used to generate a response message corresponding to the data writing transaction according to the response results of each slave database group in the database cluster.
A database cluster system, comprising:

A master database, a plurality of slave databases, and a database cluster management device configured on the master database;

The database cluster management device writes the data to be written into a master database in the database cluster in response to the data writing transaction, and transmits the data from the master database to multiple slave databases in the database cluster;

The database cluster management device determines the response results of each slave database group in the database cluster according to the response message received by the master database; the response message is sent by the slave database that successfully writes the data to be written;

The database cluster management device generates a response message corresponding to the data write transaction according to the response results of each slave database group in the database cluster.
An electronic device, comprising:

One or more processors;

A storage device for storing one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6.
A computer readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method according to any one of claims 1 to 6.