CN112286723A

CN112286723A - Computer room disaster recovery control method, terminal and storage medium

Info

Publication number: CN112286723A
Application number: CN202011069024.4A
Authority: CN
Inventors: 石鹏; 宋磊
Original assignee: Beijing Dami Technology Co Ltd
Current assignee: Beijing Dami Technology Co Ltd
Priority date: 2020-09-30
Filing date: 2020-09-30
Publication date: 2021-01-29

Abstract

The application discloses a computer room disaster recovery control method, a terminal and a storage medium. The computer room disaster recovery control method comprises the steps that when the first user terminal detects that the first cluster fails, a first instruction is generated, and the first instruction is used for indicating the second user terminal to acquire target storage information in the cache database; and sending the first instruction to the second user terminal so that the second user terminal reads a message from the target storage information at a corresponding message position in the second cluster as a message reading start site. According to the scheme, disaster recovery processing is realized when the main computer room fails, and after the main computer room fails and is switched to the standby computer room, backlog messages which are not processed in the original main computer room cluster can still be consumed continuously, and the messages are basically not repeated.

Description

Computer room disaster recovery control method, terminal and storage medium

Technical Field

The present application relates to the field of computer room disaster tolerance, and in particular, to a computer room disaster tolerance control method, a terminal, and a storage medium.

Background

kafka is a common message queue middleware, and for a system with high availability requirement, when the system strongly depends on kafka, if the machine room where the kafka is located fails, the kafka is required to provide disaster tolerance capability across the machine room. The current existing solution is to respectively deploy two sets of kafka clusters in two machine rooms, when one machine room fails, the kafka traffic of the failed machine room is switched to the kafka of the other machine room, and the server consuming the kafka by the service also consumes the kafka of the other machine room. The problem with this solution is that if the messages of kafka of the faulty room are backlogged, the backlogged messages cannot be consumed in time when switching to another room, which is unacceptable for some traffic scenarios.

Disclosure of Invention

In order to solve the above problem, embodiments of the present application provide a computer room disaster recovery control method, a terminal, and a storage medium.

In a first aspect, an embodiment of the present application provides a computer room disaster recovery control method, where the method includes the following steps:

when the first user terminal detects that the first cluster fails, generating a first instruction, wherein the first instruction is used for instructing the second user terminal to acquire target storage information in the cache database, the cache database comprises storage information, and the storage information is generated based on the first user terminal receiving a confirmation identifier sent by the first consumer client terminal;

sending the first instruction to the second user terminal so that the second user terminal reads a message from the target storage information at a corresponding message position in the second cluster as a message reading start site;

when the first user terminal detects that the first cluster is repaired, target return storage information in the cache database is obtained; the cache database comprises returned storage information, and the returned storage information is generated based on the second user terminal;

and returning the storage information from the target to serve as a message reading starting point reading message at a corresponding message in the first cluster.

Optionally, before generating the first instruction when the first user terminal detects that the first cluster is faulty, the method further includes:

when the confirmation identifier is received, generating storage information of a message corresponding to the confirmation identifier, wherein the storage information comprises a sequence number;

and sending the storage information to the cache database, and sending the serial number to the first cluster.

Optionally, the sending the storage information to the cache database and the serial number to the first cluster includes:

recording the quantity of the stored information;

when the quantity of the storage information is larger than the preset quantity, all the storage information is sent to the cache database in batches, and the serial numbers corresponding to all the storage information are sent to the first cluster in batches.

In a second aspect, the present application provides a computer room disaster recovery control method, including the following steps:

when the first cluster fails, the second user terminal receives a first instruction sent by the first user terminal, and acquires target storage information in the cache database, wherein the first instruction is used for instructing the second user terminal to acquire the target storage information in the cache database, the cache database comprises storage information, and the storage information is generated based on the first user terminal receiving a confirmation identifier sent by the first consumer client terminal;

and determining a message reading starting point based on the target storage information, and reading the message from the second cluster according to the message reading starting point.

Optionally, the storage information comprises a serial number;

when the first cluster fails, the second user terminal receives a first instruction sent by the first user terminal, and acquires target storage information in the cache database, including:

receiving a first instruction sent by the first user terminal, and acquiring a sequence number group corresponding to the storage information written in batch at the last time from the cache database, wherein the sequence number group comprises serial numbers of all the storage information written in batch in the same batch and sorted according to the generation time;

acquiring the corresponding storage information of the last serial number in the serial number group in the cache database;

and determining the storage information as target storage information.

Optionally, the target storage information includes a serial number, identification information, and a timestamp;

the determining a message reading start point based on the target storage information, and reading a message from the second cluster according to the message reading start point includes:

acquiring a message with the same sequence number as the target storage information in the second cluster, and acquiring identification information of the message;

determining whether the identification information of the message is consistent with the identification information of the target storage information;

if the position of the message is consistent with the position of the message, the message is read from the second cluster by taking the position of the message as a message reading starting point;

and if the target storage information is inconsistent with the target storage information, reading the message from the second cluster by taking the message corresponding to the timestamp of the target storage information in the second cluster as a message reading starting point.

In a third aspect, an embodiment of the present application provides a first user terminal, where the terminal includes:

a generating module, configured to generate a first instruction when the first cluster fault is detected, where the first instruction is used to instruct the second user terminal to obtain target storage information in the cache database, where the cache database includes storage information, and the storage information is generated based on a confirmation identifier sent by the first consumer client terminal and received by the first user terminal;

a sending module, configured to send the first instruction to the second user terminal, so that the second user terminal reads a message from a message corresponding to the target storage information in the second cluster as a message reading start point;

the acquisition module is used for acquiring target return storage information in the cache database when the first user terminal detects that the first cluster is repaired; the cache database comprises returned storage information, and the returned storage information is generated based on the second user terminal;

and the reading module is used for returning the storage information from the target to be used as a message reading starting point reading message at a corresponding message in the first cluster.

In a fourth aspect, an embodiment of the present application provides a first user terminal, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program to implement the steps of the method as provided in the first aspect or any one of the possible implementation manners of the first aspect.

In a fifth aspect, an embodiment of the present application provides a second user terminal, where the terminal includes:

the receiving module is used for receiving a first instruction sent by the first user terminal and acquiring target storage information in the cache database;

and the starting point determining module is used for determining a message reading starting point based on the target storage information and reading the message from the second cluster according to the message reading starting point.

In a sixth aspect, an embodiment of the present application provides a second user terminal, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor executes the computer program to implement the steps of the method as provided in the second aspect or any one of the possible implementations of the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method as provided in the first aspect or any one of the possible implementation manners of the first aspect.

In an eighth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method as provided in the second aspect or any one of the possible implementations of the second aspect.

In one or more embodiments of the present application, when detecting that a first cluster is faulty, a first user terminal may generate a first instruction and send the first instruction to a second user terminal, and after receiving the first instruction, the second user terminal may obtain last-stored target storage information from storage information sent from the first user terminal to a cache database, and determine a message reading start point from a second cluster in which a first cluster message is synchronized based on the target storage information to continue reading messages. Through the scheme, due to the fact that the messages of the first cluster and the second cluster are synchronous, when the first cluster fails, namely the messages cannot be read from the first cluster, the second user terminal can determine where the messages in the first cluster have been read before the failure according to the storage information stored in the cache database, and continuously read the messages from the second cluster, so that disaster recovery processing when the main computer room fails is achieved, it is guaranteed that after the main computer room fails and is switched to the standby computer room, the backlog messages which are not processed in the original main computer room cluster can still be continuously consumed, and the messages are basically not repeated.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

Fig. 1 is a schematic structural diagram of a computer room disaster recovery control system according to an embodiment of the present disclosure;

fig. 2 is a schematic flow chart of a method for controlling disaster tolerance of a machine room according to an embodiment of the present application;

fig. 3 is a schematic flow chart of another method for controlling disaster recovery in a computer room according to an embodiment of the present application;

fig. 4 is a schematic flow chart of another method for controlling disaster recovery in a computer room according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a first user terminal according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a second user terminal according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of another first user terminal according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of another second user terminal according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.

In the following description, the terms "first" and "second" are used for descriptive purposes only and are not intended to indicate or imply relative importance. The following description provides embodiments of the present application, where different embodiments may be substituted or combined, and thus the present application is intended to include all possible combinations of the same and/or different embodiments described. Thus, if one embodiment includes feature A, B, C and another embodiment includes feature B, D, then this application should also be considered to include an embodiment that includes one or more of all other possible combinations of A, B, C, D, even though this embodiment may not be explicitly recited in text below.

The following description provides examples, and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements described without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the described methods may be performed in an order different than the order described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined into other examples.

It should be noted that kafka is a message system based on publish and subscribe. It is commonly referred to as a "distributed commit log" or "distributed streaming platform". It is characterized by the ability to provide high throughput for both distribution and subscription. Kafka can produce about 25 thousand messages per second (50MB) and process 55 thousand messages per second (110 MB). Whereas kafka generally consists of three parts: the kafka producer client terminal (producer, i.e. the generator of the message), the kafka cluster, and the kafka consumer client terminal (consumer, i.e. the consumer of the message), the kafka producer client terminal is responsible for writing the message into the kafka cluster, one or more brokers (i.e. caching agents) are included in the kafka cluster, and one or more servers in the kafka cluster are collectively called borker), and the kafka consumer client terminal is responsible for reading the message written in the kafka cluster and consuming the message.

In the embodiment of the application, in order to avoid that the kafka client frequently upgrades to influence services, a kafka producer agent terminal and a kafka consumer agent terminal are added, the kafka producer client terminal and the kafka consumer client terminal only produce and consume messages, and the kafka producer agent and the kafka consumer agent are also used for traffic scheduling, disaster recovery and other works.

Referring to fig. 1, fig. 1 is a schematic structural diagram of a computer room disaster recovery control system according to an embodiment of the present disclosure.

As shown in fig. 1, the computer room disaster recovery control system may include a first computer room 10 and a second computer room 20, where the first computer room 10 includes a first producer client terminal 101, a first producer agent terminal 102, a first cluster 103, a first user terminal 104, and a first consumer client terminal 105, and the second computer room 20 includes a second cluster 201, a second user terminal 203, and a cache database 202. The first machine room 10 and the second machine room 20 may be two machine rooms located at different geographical locations.

One cluster may have a plurality of servers, and one server may be regarded as a spoke, that is, the first cluster 103 and the second cluster 201 may be a server group integrating a plurality of servers.

The producer client terminal may be a message producer, which only produces messages to be written to the cluster terminal by the producer proxy terminal, and the first producer client terminal 101 may be a user terminal carrying a producer client.

The producer agent terminal is a message producing agent which is set for avoiding the influence of the frequent upgrade of the client terminal on the service, and writes the message into the cluster terminal instead of the producer client terminal, and is also responsible for the work of flow scheduling, disaster tolerance and the like. The first producer agent terminal 102 may be a server loaded with producer agent software. The first producer agent terminal 102 will write the message written in the first cluster 103 into the second cluster 201 synchronously, so that the messages of the first cluster 103 and the second cluster 201 are synchronous, which is convenient for disaster recovery processing when the machine room fails.

The message consumption agent terminal is set for avoiding the influence of frequent upgrade of the client on the service, and is used for replacing the client terminal of the consumer to read the message from the cluster and is also responsible for the work of flow scheduling, disaster tolerance and the like. The first user terminal 104 and the second user terminal 203 may be servers loaded with consumer proxy software.

The consumer client terminal is a message consumer and is responsible for monitoring messages read by the consumer proxy terminal from the cluster. When the customer client terminal monitors that the customer agent terminal reads the new message, the message is pulled to be processed by the service. The first consumer client terminal 105 may be a user terminal hosting a consumer client.

The cache database 202 is a redis, and is configured to store relevant information corresponding to consumed messages to quickly find backlog messages when a machine room fails, and the cache database 202 may be a server loaded with stored information.

Possibly, the redis may be a separately installed server dedicated to storing the stored information.

Possibly, the redis may be integrated into other servers (e.g., a second cluster server, a second consumer proxy server, etc.) to reduce the footprint of server resources.

Illustratively, when a teacher wants to red-envelope students in a class group, the terminal used by the teacher to send the red-envelope is the first producer client 101, and the red-envelope message produced by the teacher is written into the first cluster 103 provided with the red-envelope theme via the first producer proxy terminal 102. The terminal used by the student to receive the red packet is the first consumer client 105, which monitors the message read by the first user terminal 104 from the first cluster 103 to find a new message sent by the teacher to send the red packet, and obtains the message, so that the student can receive the red packet information sent by the teacher to receive the red packet, and receive the red packet. When the first cluster 103 fails in the red packet sending process, the first user terminal 104 sends an instruction to the second user terminal 203, so that the second user terminal 203 determines where the red packet message sending process has progressed from the redis, and continues to send subsequent red packet messages from the location.

Under normal conditions, the system can take the first machine room 10 as a main machine room, the main machine room receives a write-in request of hundreds of service directions at ordinary times, and can take the second machine room 20 as a standby machine room, and when the main machine room fails, the flow of the main machine room is received.

Referring to fig. 2, fig. 2 is a schematic flow chart of a computer room disaster recovery control method according to an embodiment of the present application. In this embodiment of the present application, the method may be applied to a computer room disaster recovery control system shown in fig. 1, and the method includes:

s201, when the first user terminal detects that the first cluster is in fault, the first user terminal generates a first instruction, the first instruction is used for indicating the second user terminal to acquire target storage information in the cache database, the cache database comprises storage information, and the storage information is generated based on the first user terminal receiving a confirmation identifier sent by the first consumer client terminal.

In this embodiment of the present application, the manner in which the first user terminal detects the failure of the first cluster may be that it cannot read a message from the first cluster. When detecting a first cluster fault, the first user terminal generates a first instruction, and the first instruction can instruct an object receiving the first instruction to acquire target storage information from storage information stored in a cache database redis to perform disaster recovery work on the machine room fault.

S202, the first user terminal sends the first instruction to the second user terminal, so that the second user terminal reads the message from the target storage information at the corresponding message position in the second cluster as a message reading starting point.

In the embodiment of the application, the first user terminal sends the generated first instruction to the second user terminal, so that the second user terminal can determine the position of message reading before the first machine room is failed according to the target storage information in the redis as a message reading start point to continue the message reading operation.

S203, the second user terminal receives the first instruction sent by the first user terminal, and obtains the target storage information in the cache database.

In this embodiment of the application, if the first cluster of the first machine room fails, the second user terminal receives the first instruction sent by the first user terminal, and obtains target storage information in the cache database redis according to the first instruction, where the cache database stores storage information generated by the first user terminal after consuming a new message, and the storage information includes target storage information corresponding to a message that is processed last before the first machine room fails.

S204, the second user terminal determines a message reading starting point based on the target storage information, and reads the message from the second cluster according to the message reading starting point.

In the embodiment of the application, after the second user terminal acquires the target storage information, a message reading start point is determined in the second cluster according to the target storage information, that is, a position to which a message in the subject has been consumed before the failure of the first computer room is determined, and the position is used as a start point for continuing to consume the message next time.

S205, when the first user side detects that the first cluster is repaired, the target return storage information in the cache database is obtained.

In this embodiment of the present application, the cache database includes return storage information, and the return storage information is generated based on the second user terminal. After the fault of the first cluster is repaired, the whole service needs to be switched back to the first cluster, so that the first user terminal acquires the target return storage information stored in the cache database, and determines a message reading start point in the first cluster according to the target return storage information.

S206, the first user terminal returns the stored information from the target and takes the information as a message reading starting point reading message at a corresponding message position in the first cluster.

In the embodiment of the application, after obtaining the target return storage information, the first user terminal determines a message reading start point in the first cluster according to the target return storage information, that is, determines which position the message of the subject has been consumed in the second cluster when the first machine side is in fault repair, and uses the position as the start point of continuing to consume the message next.

Through the steps, disaster recovery processing is realized when the main computer room fails, and after the main computer room fails and is switched to a standby computer room, backlog information which is not processed in the original main computer room cluster can still be consumed continuously, and the information is basically not repeated.

Referring to fig. 3, fig. 3 is a schematic flow chart of another computer room disaster recovery control method provided in the embodiment of the present application. As shown in fig. 3, in the embodiment of the present application, the method may be applied to the computer room disaster recovery control system shown in fig. 1, and the method includes:

s301, when the first user terminal receives the confirmation identifier, generating storage information of the message corresponding to the confirmation identifier, wherein the storage information comprises a serial number.

In this embodiment, after the first consumer client terminal monitors a new message and finishes pulling a service, it will return an acknowledgement ack to the first user terminal to identify that the pulled message service is finished, after receiving the acknowledgement sent by the first consumer client terminal, the first user terminal will generate storage information of the message corresponding to the acknowledgement, the storage information is used to facilitate searching of related messages when disaster is tolerated, the storage information may include topic information corresponding to the message in the first cluster, group team information of the message under the topic, offset information (a continuous serial number for locating each message appended to a partition), and a timestamp (data generated by using a digital signature technique) for confirming the time when the message is written into the first cluster, the object of the signature includes information such as original file information, signature parameters, signature time, and the like), and ID unique to each message, that is, identification information.

S302, the first user terminal sends the storage information to the cache database and sends the serial number to the first cluster.

In this embodiment, the first user terminal sends the generated storage information to the redis, and at the same time, the first user terminal sends the offset information of the message to the first cluster. The former is used to ensure that the second user terminal can obtain the stored information from the redis to determine the location to continue processing the message when the first cluster fails, and the latter is used to indicate that the message has been consumed by sending the offset of the consumed message to the first cluster when the first cluster does not fail, thereby ensuring that the first consumer client terminal does not repeatedly obtain the processed message.

In an implementation manner, step S302 specifically includes:

recording the quantity of the stored information;

In the embodiment of the application, the first user terminal immediately sends out the generated storage information after each message is processed, which causes a large burden on the server, so that the first user terminal records the amount of the storage information at the moment after each piece of storage information is generated, and when the amount of the storage information is accumulated to reach a preset amount, the first user terminal sends all the accumulated storage information and serial numbers in batch. The preset number may be 5 or 10, and the specific number may be set by a worker in advance according to the message consumption speed, and is not limited.

S303, when the first user terminal detects that the first cluster is faulty, the first user terminal generates a first instruction, where the first instruction is used to instruct the second user terminal to obtain target storage information in the cache database, where the cache database includes storage information, and the storage information is generated based on that the first user terminal receives a confirmation identifier sent by the first consumer client terminal.

The specific process is shown in step S201, and is not described herein again.

S304, the first user terminal sends the first instruction to the second user terminal, so that the second user terminal reads the message from the target storage information at the corresponding message position in the second cluster as a message reading starting point.

The specific process is shown in step S202, and is not described herein again.

S305, the second user terminal receives the first instruction sent by the first user terminal, and obtains target storage information in the cache database.

The specific process is shown in step S203, and is not described herein again.

S306, the second user terminal determines a message reading starting point based on the target storage information, and reads the message from the second cluster according to the message reading starting point.

The specific process is shown in step S204, and is not described herein again.

In one embodiment, the number of servers and the number of partitions of the first cluster and the second cluster are the same.

In this embodiment of the application, after the first machine room is down, it is desirable to retrieve which message has been consumed by the corresponding group under the topic of the first machine room in the second machine room and consume the message, that is, it is desirable to make the offset of the first machine room reusable in the second machine room, it is necessary to ensure that the number of brokers in the first machine room and the second machine room is consistent with the number of partitions, and when the first producer agent terminal writes a message into the cluster, the load balancing algorithm of which partition the message falls on does not use the random algorithm, and it is possible to use the hash algorithm and the like to ensure that the message falls on the same partition in both the two machine rooms.

S307, when the first user side detects that the first cluster is repaired, the target return storage information in the cache database is obtained.

The detailed process is as described in step S205, and therefore, will not be described herein again.

S308, the first user terminal returns the stored information from the target and takes the information as a message reading starting point reading message at the corresponding message position in the first cluster.

The detailed process is as described in step S206, and therefore, is not described herein again.

Through the steps, the generation and the sending of the stored information when the main computer room is not in fault are completed, and meanwhile, the serial number in the stored information is sent to the cluster of the main computer room to ensure the normal consumption of the information when the main computer room is not in fault, the disaster recovery processing when the main computer room is in fault is also realized, the overstock information which is not processed in the cluster of the original main computer room can still be continuously consumed after the main computer room is switched to the standby computer room after the main computer room is in fault, and the information is basically not repeated.

Referring to fig. 4, fig. 4 is a schematic flow chart of a computer room disaster recovery control method according to an embodiment of the present application. As shown in fig. 4, in the embodiment of the present application, the method may be applied to the computer room disaster recovery control system shown in fig. 1, and the method includes:

s401, when the first user terminal detects the first cluster fault, the first user terminal generates a first instruction.

The specific process is shown in step S201, and is not described herein again.

S402, the first user terminal sends the first instruction to the second user terminal.

The specific process is shown in step S202, and is not described herein again.

And S403, the second user terminal receives the first instruction sent by the first user terminal, and obtains a sequence number group corresponding to the storage information written in batch at the last time from the cache database, wherein the sequence number group comprises the sequence numbers of all the storage information written in batch in the same batch and sorted according to the generation time.

In the embodiment of the present application, in order to alleviate the burden on the server caused by message sending and receiving, the first user terminal does not write the storage information into the cache database redis immediately after generating the storage information, but writes the storage information in batch after the amount of the accumulated storage information is greater than the preset amount. The stored information may include topic information corresponding to the message in the first cluster, group team information under the topic for the message, offset information (a consecutive sequence number for locating each message appended to the partition) for confirming the specific location of the message in the queue, a timestamp (data generated using digital signature technology, the signed object includes information of original file information, signature parameters, signature time, etc.), and an ID unique to each message, i.e., identification information.

After receiving the first instruction, the second user terminal obtains a sequence number group formed by sequence numbers corresponding to the last batch of storage information written in the redis by the first user terminal in batch from the redis.

S404, the second user terminal obtains the corresponding storage information of the last serial number in the serial number group in the cache database.

In this embodiment, the sequence numbers arranged in the sequence number group are necessarily sequentially ordered according to the time generated by the storage information, so that the message corresponding to the last sequence number in the sequence number group is the last message processed before the failure of the first cluster, and the first user terminal will obtain the storage information corresponding to the last sequence number.

S405, the second user terminal determines the storage information as target storage information.

In this embodiment of the application, after obtaining the storage information corresponding to the last serial number, the first user terminal determines the storage information as the target storage information.

S406, the second user terminal acquires the message with the same sequence number as the target storage information in the second cluster, and acquires the identification information of the message.

In the embodiment of the present application, although the message in the second cluster is synchronized with the message in the first cluster, in practice, there may be a case where the transmission process of the message is jittered, or there is a written message already in the first cluster before synchronization, and the sequence numbers are generated by sequentially arranging the sequence numbers in sequence, which may result in that the sequence numbers of the same message in the first cluster and the second cluster may be different. Therefore, the second user terminal first finds the message with the same sequence number as the sequence number in the target storage information from the second cluster, and obtains the identification information of the message.

S407, the second user terminal determines whether the identification information of the message is consistent with the identification information of the target storage information;

In the embodiment of the present application, the identification information of each message, i.e. the message ID, is separate and unique, and the second user terminal will determine whether the identification information of the message found in the second cluster is consistent with the identification information in the target storage information. If the two identification information are consistent, the second user terminal considers that the message in the second cluster is the last message consumed before the first machine room is failed, and the position of the message is used as a message reading starting point to continuously read the message. If the two identification information are not consistent, it indicates that there may be a jitter or other reasons when the messages are synchronized, so that the message corresponding to the sequence number in the second cluster is not the message corresponding to the target storage information, the second user terminal acquires the timestamp in the target storage information, determines the target message in the second cluster by using the time point of message writing, and reads the message from the second cluster by using the message as a message reading start point.

S408, when the first user side detects that the first cluster is repaired, the target return storage information in the cache database is obtained.

S409, the first user terminal returns the stored information from the target and takes the information as the information reading starting point reading information at the corresponding information position in the first cluster.

Through the steps, the first user terminal submits information such as offset to the redis, and when the machine room is in failure, after the machine room flow is switched and before the second user terminal consumes the message, the information such as offset is obtained from the redis to continue the last consumption of the first machine room, so that the disaster tolerance processing when the main machine room is in failure is realized, and after the main machine room is in failure and is switched to the standby machine room, the backlog message which is not processed in the original main machine room cluster can still be consumed continuously, and the message is basically not repeated.

It should be noted that, after the failure of the first machine room is recovered, the first user terminal obtains the returned storage information from the cache database, and determines a message reading start point from the first cluster based on the returned storage information to read the message, where the returned storage information is the last storage information generated after the second user terminal consumes the message in the second cluster when the first machine room is failed. The first user terminal can determine where the message in the second cluster is read according to the returned storage information, and accordingly determines the corresponding position of the message in the first cluster, and the position is used as a message reading starting point to continue reading the message, so that the service is switched back to the first machine room. In the process of the failure of the first machine room, the second cluster is still written with messages, so that the messages corresponding to the returned storage information may not be written into the first cluster and cannot be found. When the corresponding message cannot be found in the first cluster, the first user terminal continuously acquires the newly generated returned storage information until the message corresponding to the returned storage information can be found in the first cluster.

The first user terminal provided in the embodiment of the present application will be described in detail below with reference to fig. 5. It should be noted that, the first user terminal shown in fig. 5 is used for executing the method of the embodiment shown in fig. 2 to 4 of the present application, and for convenience of description, only the portion related to the embodiment of the present application is shown, and details of the specific technology are not disclosed, please refer to the embodiment shown in fig. 2 to 4 of the present application.

Referring to fig. 5, fig. 5 is a schematic structural diagram of a first user terminal according to an embodiment of the present application, and as shown in fig. 5, the first user terminal is applied to the system shown in fig. 1, and the terminal includes:

a generating module 501, configured to generate a first instruction when detecting that the first cluster is faulty, where the first instruction is used to instruct the second user terminal to obtain target storage information in the cache database, where the cache database includes storage information, and the storage information is generated based on that the first user terminal receives a confirmation identifier sent by the first consumer client terminal;

a sending module 502, configured to send the first instruction to the second user terminal, so that the second user terminal reads a message from a message corresponding to the target storage information in the second cluster as a message reading start point;

an obtaining module 503, configured to obtain target return storage information in the cache database when the first user terminal detects that the first cluster has failed to be repaired; the cache database comprises returned storage information, and the returned storage information is generated based on the second user terminal;

a reading module 504, configured to return, from the target, the stored information as a message reading start point reading message at a corresponding message in the first cluster.

In an implementation, the generating module 501 is further configured to:

the sending module 502 is further configured to:

In an implementation manner, the sending module 502 specifically includes:

a recording unit configured to record the amount of the storage information;

and the judging unit is used for sending all the stored information to the cache database in batch and sending the serial numbers corresponding to all the stored information to the first cluster in batch when the number of the stored information is greater than the preset number.

It is clear to a person skilled in the art that the solution according to the embodiments of the present application can be implemented by means of software and/or hardware. The "unit" and "module" in this specification refer to software and/or hardware that can perform a specific function independently or in cooperation with other components, where the hardware may be, for example, a Field-Programmable Gate Array (FPGA), an Integrated Circuit (IC), or the like.

Each processing unit and/or module in the embodiments of the present application may be implemented by an analog circuit that implements the functions described in the embodiments of the present application, or may be implemented by software that executes the functions described in the embodiments of the present application.

Referring to fig. 6, a schematic structural diagram of a first user terminal according to an embodiment of the present application is shown, where the first user terminal may be used to implement the methods in the embodiments shown in fig. 2 to fig. 4. As shown in fig. 6, the first user terminal 600 may include: at least one central processor 601, at least one network interface 604, a user interface 603, a memory 605, at least one communication bus 602.

Wherein a communication bus 602 is used to enable the connection communication between these components.

The user interface 603 may include a Display screen (Display) and a Camera (Camera), and the optional user interface 603 may also include a standard wired interface and a wireless interface.

The network interface 604 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface).

Central processor 601 may include one or more processing cores, among others. The central processor 601 connects the various parts within the overall terminal 600 using various interfaces and lines, and performs various functions of the terminal 600 and processes data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 605, and calling data stored in the memory 605. Optionally, the central Processing unit 601 may be implemented in at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The Central Processing Unit 601 may integrate one or a combination of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing the content required to be displayed by the display screen; the modem is used to handle wireless communications. It is understood that the modem may not be integrated into the central processor 601, but may be implemented by a single chip.

The Memory 605 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 605 includes a non-transitory computer-readable medium. The memory 605 may be used to store instructions, programs, code, sets of codes, or sets of instructions. The memory 605 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 605 may alternatively be at least one storage device located remotely from the central processor 601. As shown in fig. 6, memory 605, which is one type of computer storage medium, may include an operating system, a network communication module, a user interface module, and program instructions.

The second user terminal provided in the embodiment of the present application will be described in detail below with reference to fig. 7. It should be noted that, the second user terminal shown in fig. 7 is used for executing the method of the embodiment shown in fig. 2 to 4 of the present application, and for convenience of description, only the portion related to the embodiment of the present application is shown, and details of the specific technology are not disclosed, please refer to the embodiment shown in fig. 2 to 4 of the present application.

Referring to fig. 7, fig. 7 is a schematic structural diagram of a second user terminal according to an embodiment of the present application, and as shown in fig. 7, the second user terminal is applied to the system shown in fig. 1, and the terminal includes:

a receiving module 701, configured to receive a first instruction sent by the first user terminal, and acquire target storage information in the cache database.

In an implementation manner, the receiving module 701 specifically includes:

a receiving unit, configured to receive a first instruction sent by the first user terminal, and obtain, from the cache database, a sequence number group corresponding to the storage information written in batch at the last time, where the sequence number group includes sequence numbers of all the storage information written in batch in the same order according to generation time;

the first acquisition unit is used for acquiring the corresponding storage information of the last serial number in the serial number group in the cache database;

a first determination unit configured to determine the storage information as target storage information.

A start point determining module 702, configured to determine a message reading start point based on the target storage information, and read a message from the second cluster according to the message reading start point.

In an implementation manner, the start position determining module 702 specifically includes:

a second obtaining unit, configured to obtain, in the second cluster, a message having a same sequence number as the target storage information, and obtain identification information of the message;

a second determination unit configured to determine whether or not the identification information of the message coincides with the identification information of the target storage information;

Referring to fig. 8, a schematic structural diagram of a second user terminal according to an embodiment of the present application is shown, where the second user terminal may be used to implement the methods in the embodiments shown in fig. 2 to fig. 4. As shown in fig. 8, the second user terminal 800 may include: at least one central processor 801, at least one network interface 804, a user interface 803, a memory 805, at least one communication bus 802.

Wherein a communication bus 802 is used to enable connective communication between these components.

The user interface 803 may include a Display screen (Display) and a Camera (Camera), and the optional user interface 803 may also include a standard wired interface and a wireless interface.

The network interface 804 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface).

The central processor 801 may include one or more processing cores, among others. The central processor 801 connects various parts within the entire terminal 800 using various interfaces and lines, and performs various functions of the terminal 800 and processes data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 805 and calling data stored in the memory 805. Alternatively, the central Processing unit 801 may be implemented in at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The CPU 801 may integrate one or a combination of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing the content required to be displayed by the display screen; the modem is used to handle wireless communications. It is to be understood that the modem may be implemented by a single chip without being integrated into the central processing unit 801.

The Memory 805 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 805 includes a non-transitory computer-readable medium. The memory 805 may be used to store instructions, programs, code sets, or instruction sets. The memory 805 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 805 may optionally be at least one memory device located remotely from the central processor 801 as previously described. As shown in fig. 8, memory 805, which is a type of computer storage media, may include an operating system, a network communication module, a user interface module, and program instructions.

The present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above-described method. The computer-readable storage medium may include, but is not limited to, any type of disk including floppy disks, optical disks, DVD, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some service interfaces, devices or units, and may be an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a memory, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned memory comprises: various media capable of storing program codes, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by a program, which is stored in a computer-readable memory, and the memory may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.

The above description is only an exemplary embodiment of the present disclosure, and the scope of the present disclosure should not be limited thereby. That is, all equivalent changes and modifications made in accordance with the teachings of the present disclosure are intended to be included within the scope of the present disclosure. Embodiments of the present disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the disclosure herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A method for controlling disaster recovery of a machine room is characterized by comprising the following steps:

2. The method according to claim 1, wherein before generating the first instruction when the first user terminal detects the first cluster failure, further comprising:

3. The method of claim 2, wherein sending the stored information to the cache database and sending the sequence number to the first cluster comprises:

recording the quantity of the stored information;

4. A method for controlling disaster recovery of a machine room is characterized by comprising the following steps:

5. The method of claim 4, wherein the stored information comprises a sequence number;

and determining the storage information as target storage information.

6. The method of claim 4, wherein the target storage information comprises a sequence number, identification information, a timestamp;

7. A first user terminal, characterized in that said terminal comprises:

8. A first user terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1-3 when executing the computer program.

9. A second user terminal, characterized in that the terminal comprises:

10. A second user terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor when executing the computer program realizes the steps of the method according to any of the claims 4-6.

11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-6.