CN114598593B - Message processing method, system, computing device and computer storage medium - Google Patents
Message processing method, system, computing device and computer storage medium Download PDFInfo
- Publication number
- CN114598593B CN114598593B CN202210141634.3A CN202210141634A CN114598593B CN 114598593 B CN114598593 B CN 114598593B CN 202210141634 A CN202210141634 A CN 202210141634A CN 114598593 B CN114598593 B CN 114598593B
- Authority
- CN
- China
- Prior art keywords
- proxy server
- message
- main
- standby
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
Abstract
The embodiment of the invention provides a message processing method and a message processing system. The message processing method is applied to the distributed message system and comprises the following steps: the method comprises the steps that under the condition that a first main proxy server fails, a first standby proxy server scans target messages meeting the delivery requirements in the first main proxy server; sending the target message to a second main proxy server; the target message is stored in a message queue of the second main proxy server for the consumer to consume the target message. The technical scheme provided by the embodiment of the invention realizes the technical effect of ensuring the normal consumption of the target message under the condition that the switching of the active and standby proxy servers is not needed.
Description
Technical Field
The embodiment of the invention relates to the field of cloud computing, in particular to a message processing method, a system, computing equipment and a computer storage medium.
Background
The RocketMQ system is a distributed, open-source, distributed message system that is widely used in the field of message processing.
In the related art, a server side of a RocketMQ system generally adopts a regional deployment mode, a Name server (route discovery server side) and a broker server side are deployed in each region, and a master-slave cold standby scheme is adopted to improve disaster recovery capability. The master-slave cold standby scheme is to deploy a master proxy server and a standby proxy server, and in a split-region deployment mode, the master proxy server and the corresponding standby proxy server are deployed in different regions, namely, the master proxy server and the standby proxy server are deployed in a mixed mode in the same region. The master proxy server is readable and writable, the standby proxy server is used as a copy of the master proxy server, has the full data on the master proxy server, can only receive the data synchronized by the master proxy server, and is readable and writable.
Because the RocketMQ supports some special types of target messages, such as timing messages, transaction messages, delay messages and the like, the target messages are firstly stored in a special Topic (theme), and when the delivery condition is met, the main server side delivers the target messages to a message queue, so that consumers can consume the target messages. In the deployment mode of the open source master-slave cold standby scheme, if a problem occurs in the proxy server of one area, for example, the primary proxy server in the first area drops, because the standby proxy server cannot maintain the target message, in order to ensure the normal consumption of the target message, the primary proxy server in the first area needs to be pulled up again. The consumption of the target message may be delayed or lost during the primary-standby handover.
Disclosure of Invention
The embodiment of the invention provides a message processing method and a message processing system.
In a first aspect, an embodiment of the present invention provides a message processing method, which is applied to a distributed message system, including:
under the condition that a first main proxy server fails, a first standby proxy server scans target messages meeting the delivery requirements in the first main proxy server;
the target message is sent to a second main proxy server; the target message is stored in a message queue of the second main proxy server for consumers to consume.
In a second aspect, an embodiment of the present invention provides a message processing method, which is applied to a distributed message system, where the method includes:
under the condition that the first main proxy server resumes work, the first main proxy server acquires the address of the first standby proxy server from the route discovery server;
the first main proxy server establishes communication connection with the first standby proxy server based on the address;
the first main proxy server acquires metadata sent by the first standby proxy server through the communication connection, so that the first main proxy server determines whether to update metadata according to the version number of the metadata, wherein the version number of the metadata is determined according to the consumption number of target messages under the condition that the first main proxy server fails, and the target messages comprise messages which are pulled from the first main proxy server by the first standby proxy server and are sent to the second main proxy server.
In a third aspect, an embodiment of the present invention provides a message processing method, which is applied to a second main proxy server of a distributed message, including:
acquiring a target message sent by a first standby proxy server; the target message is obtained by scanning a first standby proxy server from the first main proxy server under the condition that the first main proxy server fails;
Storing the target message in a message queue for consumers to consume the target message from the message queue.
In a fourth aspect, an embodiment of the present invention provides a first proxy server, including a scanning module and a sending module.
The scanning module is used for scanning target messages meeting the delivery requirements in the first main proxy server under the condition that the first main proxy server fails;
the sending module is used for sending the target message to a second main proxy server; the target message is stored in a message queue of the second main proxy server for consumers to consume.
In a fifth aspect, in an embodiment of the present invention, a second main proxy server is provided, including:
the target message acquisition module is used for acquiring a target message sent by a first standby proxy server, wherein the target message is obtained by scanning the first standby proxy server from a first main proxy server under the condition that the first main proxy server fails;
and the storage module is used for storing the target message into a message queue so as to enable a consumer to consume the target message from the message queue.
In a sixth aspect, in an embodiment of the present invention, a first main proxy server is provided, including:
the address acquisition module is used for acquiring the address of the first standby proxy server from the route discovery server under the condition that the first main proxy server resumes working;
the connection establishment module is used for establishing communication connection with the first standby proxy server based on the address;
the metadata acquisition module is used for acquiring metadata sent by the first backup proxy server through the communication connection so that the first main proxy server can determine whether metadata update is performed according to the version number of the metadata, wherein the version number of the metadata is determined according to the consumption number of target information under the condition that the first main proxy server fails, and the target information comprises information which is pulled from the first main proxy server by the first backup proxy server and is sent to the second main proxy server.
In a seventh aspect, in an embodiment of the present invention, a computing device includes a processing component and a storage component;
the processing component is used for running the first standby proxy server and/or the second main proxy server;
the storage component stores one or more computer instructions; the one or more computer instructions are configured to be invoked and executed by the processing component to implement a message processing method as provided by an embodiment of the present invention.
In an eighth aspect, in an embodiment of the present invention, there is provided a computer storage medium storing a computer program, where the computer program is executed by a computer to implement a message processing method provided in the embodiment of the present invention.
In the embodiment of the invention, under the condition that the first main proxy server fails, the first standby proxy server corresponding to the first main proxy server is utilized to scan the target message meeting the delivery requirement in the first main proxy server, and the target message is sent to the second main proxy server which is deployed in the same physical machine as the first standby proxy server, so that the consumer consumes the target message from the consumption queue of the second main proxy server.
These and other aspects of the invention will be more readily apparent from the following description of the embodiments.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions of the prior art, the following description will briefly explain the drawings used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a message queuing system according to the present invention;
FIG. 2 is a flow chart of one embodiment of a message processing method provided by an embodiment of the present invention;
FIG. 3 schematically illustrates a timeline diagram of the receipt of a target message and a first primary proxy server side failure;
FIG. 4 is a flow chart of one embodiment of a message processing method according to another embodiment of the present invention;
FIG. 5 schematically illustrates a message processing method in the case where the first primary proxy server resumes operation;
FIG. 6 is a flow chart of an embodiment of a message processing method according to another embodiment of the present invention;
FIG. 7 is a block diagram of a message processing system according to an embodiment of the present invention;
FIG. 8 is a block diagram of a first proxy server provided in an embodiment of the present invention;
FIG. 9 is a block diagram of a second primary proxy server provided in an embodiment of the present invention;
FIG. 10 is a block diagram of a first primary proxy server provided in an embodiment of the present invention;
FIG. 11 is a block diagram of a computing device provided by an embodiment of the present invention.
Detailed Description
In order to enable those skilled in the art to better understand the present invention, the following description will make clear and complete descriptions of the technical solutions according to the embodiments of the present invention with reference to the accompanying drawings.
In some of the flows described in the specification and claims of the present invention and in the foregoing figures, a plurality of operations occurring in a particular order are included, but it should be understood that the operations may be performed out of order or performed in parallel, with the order of operations such as 101, 102, etc., being merely used to distinguish between the various operations, the order of the operations themselves not representing any order of execution. In addition, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first" and "second" herein are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, and are not limited to the "first" and the "second" being different types.
The technical scheme provided by the embodiment of the invention can be applied to the distributed message system, and is used for enabling the target message stored by the main proxy server to be normally consumed under the condition that the main proxy server of the distributed message system fails.
The RocketMQ system is a distributed and open-source distributed message system, has the characteristics of low delay, high concurrency, high availability, high reliability and the like, and is widely applied in the field of message processing. The RocketMQ system, like other types of distributed messaging systems, supports the publishing and subscription of messages, while also supporting the implementation of some targeted messages, such as transaction messages, timing messages, delay messages, and the like.
The distributed messaging system may include a producer, a consumer, and a server. For ease of understanding, as shown in fig. 1, a schematic structural diagram of a distributed message system is shown, where the distributed message system may include a Producer (Producer) 101, a Consumer (Consumer) 102, a route discovery server (Name server) 103, and a proxy server (Broker server) 104, where the Producer, the Consumer, the route discovery server, and the proxy server may all be deployed in a cluster form and are composed of a plurality of nodes, and the Producer and the Consumer are clients with respect to the route discovery server and the proxy server. In one practical application, for example, the RocketMQ system is implemented using the architecture shown in FIG. 1.
In connection with the system architecture diagram shown in fig. 1, the following description will first be given of technical terms that may be referred to herein:
message (message): and a carrier for carrying and transmitting information in the message queue.
Topic (theme): a message type, the published message belongs to a certain type, which is called Topic.
Proxy server (Broker server): the nodes providing the publish/subscribe function in the distributed message system are responsible for storing messages, forwarding messages, etc. for message transfer roles.
Message queues: each Topic will store messages by one to multiple message queues.
Route discovery server (Name server): the nodes in the distributed message system for storing routing information may include a list of the brooker servers and a list of topics in the brooker servers. The list of the affiliated brooklervers of publish/subscribe topic can be obtained through Name server. After the Broker server is started, a registration request is sent to each Name server, and metadata such as an address and a Topic list of the Broker server are reported.
Producer (Producer): also known as message publishers, are responsible for producing and sending messages. In the distributed message system, a producer randomly establishes a long connection with a route discovery server, acquires a Broker server where a Topic of a message to be issued is located from the long connection, establishes the long connection with the Broker server, and periodically sends a heartbeat packet to the Broker server.
Consumer (Consumer): also known as message subscribers, are responsible for receiving and consuming messages. In the distributed message system, the consumer also establishes a long connection with a route discovery server at random, obtains the Broker server where the subscribed Topic is located from the long connection with the Broker server, and then establishes the long connection with the Broker server.
Timing message: the Producer sends a message to the Broker server, but does not expect this message to be delivered immediately, but delays delivery to the Consumer for consumption until some time after the current point in time, i.e., a timed message. Timing information issued by a producer is temporarily stored in the information storage component, and is written into the information queue after a certain time is reached.
Delay message: the Producer sends the message to the Broker server, but does not expect the message to be delivered immediately, but delays it for a certain time before it is delivered to the Consumer for consumption, i.e. delays the message. Timing information issued by a producer is temporarily stored in the information storage component, and is written into the information queue after a certain time delay.
Transaction message: the messages are consumed simultaneously or not, and the messages with the characteristics are transaction messages. The method comprises the steps that a producer can issue a plurality of half-transaction messages carrying the same transaction identifier, a Broker server stores the half-transaction messages temporarily in a storage engine, the transaction execution of the producer is finished, a confirmation request is sent to the Broker server, and the Broker server writes the plurality of half-transaction messages temporarily stored in the same transaction into a message queue as transaction information.
Message store component (CommitLog): all messages received by the RocketMQ are saved.
Metadata, data in the RocketMQ for recording consumption, delivery status, such as consumption sites, timed message playback sites, etc.
The Raft consensus algorithm, a strongly consistent, decentralised, highly available distributed protocol, can be used for handover election.
RTO (Recovery Time Objective ) is the time in units of time, i.e. the time after a disaster has occurred, from the stop of the information system or business function to the time that it has to be recovered.
RPO (Recovery Point Object, recovery point objective), which refers to a past point in time when data can be recovered after a disaster or emergency event, is the amount of data loss that can be tolerated by the business system.
In the related art, a server side of a distributed message system generally adopts a partition deployment mode, a Name server (route discovery server side) and a broker server side are deployed in each region, and a master-slave cold standby scheme is adopted to improve disaster recovery capability. The master-slave cold standby scheme is to deploy a master proxy server and a standby proxy server, and in a split-region deployment mode, the master proxy server and the corresponding standby proxy server are deployed in different regions, namely, the master proxy server and the standby proxy server are deployed in a mixed mode in the same region. The master proxy server is readable and writable, the standby proxy server is used as a copy of the master proxy server, has the full data on the master proxy server, can only receive the data synchronized by the master proxy server, and is readable and writable.
Because the distributed message supports some special types of target messages, such as timing messages, transaction messages, delay messages and the like, the target messages are firstly stored in the special Topic, and when the delivery condition is met, the main server side delivers the target messages to the message queue, so that consumers can consume the target messages. In the deployment mode of the open source master-slave cold standby scheme, if a problem occurs in the proxy server of one area, for example, the primary proxy server in the first area is disconnected, and the standby proxy server cannot maintain the target message, in order to ensure the normal consumption of the target message, the standby server deployed in the second area needs to be manually pulled into the primary proxy server, or the primary proxy server in the first area is pulled up again. The consumption of the target message may be delayed or lost during the primary-standby handover.
A Raft thermal solution is also adopted in the related art to improve disaster recovery capability. The Raft hot standby scheme can be used for overcoming the defect that the proxy server group in the master-slave cold standby scheme has no automatic fault transfer capability, namely, after the main proxy server fails, the standby proxy server needs to be manually pulled into the main proxy server.
After the main proxy server fails, the Raft hot standby scheme can automatically select a new main proxy server from the system to provide service through a Raft algorithm.
The advantages of the Raft hot-standby are that failover (failover) can be accomplished without relying on external components, but due to the limitations of the Raft algorithm, the Raft hot-standby must guarantee a deployment of three copies and more within the proxy server-side group, with low resource utilization, and due to the limitations of the Raft algorithm based on multiple groups, there is a long election time when performing failover.
In addition, there are zookeeper-based thermal alternatives in the related art. The zookeeper-based hot-standby relies on the external components zookeeper and Controller to ensure high availability, providing switching capability at failure. The zookeeper function is mainly a mechanism for storing a state machine in a persistent mode, storing the state of a proxy server in a temporary node mode and providing a state change notification. The Controller component observes the change of the proxy server state through the zookeeper, executes the state machine change and pushes the new state machine to the zookeeper. The proxy server reports the state of the proxy server to the zookeeper, and monitors the change of a storage state machine in the zookeeper to finish the fault transfer.
The disadvantage of zookeeper-based hot-standby is that it relies on external components zookeeper and Controller, which bring additional operational burden and longer election time when performing failover because zookeeper-consistent ZAB protocol is based on the requirements of multiple genres.
In order to at least partially solve the technical problems existing in the related art, in the embodiment of the invention, in order to improve the disaster tolerance of the distributed message system, ensure that the target message stored by the main proxy server can be consumed normally under the condition of the failure of the main proxy server of the distributed message system, the inventor provides a technical scheme of the invention through a series of researches, and in the embodiment of the invention, the first standby proxy server scans the target message meeting the delivery requirement in the first main proxy server under the condition of the failure of the first main proxy server; the target message is sent to a second main proxy server which is deployed in the same physical machine as the first standby proxy server; the target message is stored in a message queue of the second main proxy server for the consumer to consume the target message.
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to fall within the scope of the invention.
Fig. 2 is a flowchart of an embodiment of a message processing method according to an embodiment of the present invention, where the method may be applied to a distributed message system, and the method may include the following steps:
and 201, under the condition that the first main proxy server fails, the first standby proxy server scans target messages meeting the delivery requirements in the first main proxy server.
According to the embodiment of the invention, the first standby proxy server can be a copy of the first main proxy server, wherein the first main proxy server is readable and writable, the first standby proxy server is used as a copy of the main proxy server and has full data on the first main proxy server, and only data synchronized by the first main proxy server can be received, and the first standby proxy server can be readable and writable.
According to the embodiment of the invention, the first standby proxy server and the first main proxy server are pre-established with a long connection communication link, and the long connection communication link is utilized to perform data synchronization in real time or periodically.
According to an embodiment of the invention, the distributed message may comprise a RocketMQ system.
According to the embodiment of the invention, the target message may be a non-real-time message supported by the RocketMQ system, that is, the target message is not expected to be consumed by a consumer immediately after being delivered to the RocketMQ system by a producer, but is consumed by the consumer after the target message meets the delivery requirement.
According to embodiments of the present invention, the delivery requirements may include, for example, arrival of delivery time or receipt of a delivery request, etc.
According to the embodiment of the invention, the target message can be a message which is sent to the RocketMQ system before the first main proxy server fails and does not meet the release requirement before the first main proxy server fails.
Fig. 3 schematically shows a timeline diagram of the reception of a target message and the failure of a first primary proxy server side.
As shown in fig. 3, 301 is a time line, and time passes are indicated in the arrow direction. A may refer to a time point when the target message is sent to the RocketMQ system, B may refer to a time point when the first main proxy server fails, and C may refer to a time point when the target message meets the delivery requirement. That is, the failure of the first main proxy server occurs between the time when the fcketmq system receives the target message and the time when the target message meets the delivery requirement, the target message is delivered yet, and the first main proxy server fails.
In the RocketMQ system, the non-real-time target message may be referred to as a secondary message, which is typically only authorized for maintenance by the primary proxy server, according to embodiments of the present invention.
Because the target message is received when the first main proxy server normally works and is not delivered before the first main proxy server fails, the failure of the first main proxy server can cause that the secondary message stored by the first main proxy server cannot be delivered normally.
In the related art, after the first primary proxy server fails, the first primary proxy server needs to be pulled up to ensure normal consumption of the secondary messages stored in the first primary proxy server. Or, the copy of the first main proxy server, i.e. the first standby proxy server, may be pulled to be the main proxy server, so that the first standby proxy server switched to be the main proxy server performs the delivery of the second-level message. However, the time to pull up the first primary proxy server or pull the first backup proxy server to the primary proxy server is typically long, and this process may result in a delay or loss of the secondary message. For example, in fig. 3, the delivery time of the target message is time point C, and the operation of pulling up the first primary proxy server or pulling up the first backup proxy server to the primary proxy server can be completed at time point D after time point C, so that the target message that should be delivered at time point C needs to be delayed until time point D to be delivered, which seriously affects the user experience.
In the embodiment of the invention, after the first main proxy server fails, the first standby proxy server can be utilized to proxy the first main proxy server to scan the target message stored in the first main proxy server, and the target message meeting the delivery requirement is pulled out so that the consumer consumes the target message meeting the delivery requirement without waiting for pulling up the first main proxy server or pulling up the first standby proxy server into the main proxy server and then scanning the target message.
202, sending the target message to a second main proxy server; the target message is stored in a message queue of the second main proxy server for the consumer to consume the target message.
According to the embodiment of the invention, due to the readable and non-writable nature of the first standby proxy server, after the first standby proxy server pulls the target message meeting the delivery requirement from the first main proxy server, the target message can be sent to another main proxy server, such as a second main proxy server.
According to the embodiment of the invention, due to the readable and writable nature of the second main proxy server side, after the second main proxy server side receives the target message, the target message can be stored in the message queue thereof for consumers to consume the target message.
According to the embodiment of the invention, the area can refer to physical isolation of the main proxy server and the standby proxy server, and the fault of the proxy server of one area can not affect the corresponding proxy server of the other area. Different areas may refer to different machine rooms.
According to the embodiment of the invention, after the target message is stored in the consumption queue of the second main agency server, the consumer only needs to pull the target message from the message queue of the second main agency server to consume the target message.
Because the high availability mechanism of the consumer client, that is, when the consumer client consumes the message, each main proxy server in the RocketMQ system is traversed until the target message expected by the main proxy server is pulled, the process that the first standby proxy server proxies the first main server to pull the target message and puts the target message into the second main proxy server is not felt by the consumer client, and the user experience is improved.
In the embodiment of the invention, under the condition that the first main proxy server fails, the first standby proxy server corresponding to the first main proxy server is utilized to scan the target message meeting the delivery requirement in the first main proxy server, and the target message is sent to the second main proxy server which is deployed in the same physical machine as the first standby proxy server, so that the consumer consumes the target message from the consumption queue of the second main proxy server. Compared with the Raft hot standby scheme and the zookeeper-based hot standby scheme in the related art, the message processing method provided by the embodiment of the invention has the advantages that the main and standby switching is not needed, the RTO time is shorter, and in addition, no extra operation and maintenance burden exists because external components are not needed.
According to the embodiment of the invention, the first standby proxy server can send the pulled target message to any one of the main proxy servers which are in the same area with the first standby proxy server and work normally. Under the condition that more than two main proxy servers working normally exist in the same area, the first standby proxy server can randomly select one to send the target message.
According to the embodiment of the invention, if the first proxy server sends the pulled target message to the second main proxy server which is not in the same physical machine as the first proxy server, more internal traffic flows are generated in the same area, and waste of network resources is caused.
According to the embodiment of the invention, the second main proxy server and the first standby proxy server are deployed in the same physical machine.
According to the embodiment of the invention, the target message is sent to the second main proxy server which is deployed in the same physical machine as the first standby proxy server, so that the technical effects of increasing the utilization rate of network resources and saving the network resources can be realized.
According to an embodiment of the present invention, step 201 may be specifically implemented as:
under the condition that the fault of the first main proxy server is monitored, starting a scanning thread corresponding to the first main proxy server;
And scanning the message storage component of the first main proxy server side by using the scanning thread so as to acquire the target message from the message storage component.
According to an embodiment of the invention, the target message is typically stored in a special Topic of the first master proxy server-side message storage component, which is not visible to the consumer, before the delivery requirements are met.
According to the embodiment of the invention, after the first main proxy server side fault is monitored, the first standby proxy server side can scan the special Topic of the first main proxy server side message storage component in real time or periodically, and pull out the target message meeting the delivery requirement after each scan.
According to the embodiment of the invention, the disaster recovery mechanism of the RocketMQ system can ensure the normal consumption of the target message, and the normal release and consumption of the common message can be performed.
According to the embodiment of the invention, each proxy server of the RocketMQ system registers with the route discovery server before being on line, after registration, each proxy server sends heartbeat to the route discovery server in work, and the route discovery server maintains a route table representing the working states of all proxy servers in the system. If a certain proxy server has a heartbeat disconnection, the route discovery server can reject the proxy server from the route table.
For example, the RocketMQ system includes a machine room A and a machine room B, wherein a first main proxy server, a second standby proxy server and a first route discovery server are deployed in the machine room A, and a first standby proxy server, a second main proxy server and a second route discovery server are deployed in the machine room B.
The first main proxy server and the second standby proxy server can register in the first route discovery server and the second route discovery server respectively before being on line, and send heartbeats to the first route discovery server and the second route discovery server respectively in operation. Correspondingly, the first standby proxy server and the second main proxy server can register in the first route discovery server and the second route discovery server respectively before being on line, and send heartbeats to the first route discovery server and the second route discovery server respectively in operation.
If the machine room A fails, namely the first main proxy server, the second standby proxy server and the first route discovery server are down, the second route discovery server discovers that the first main proxy server and the second standby proxy server are disconnected by heartbeat, so that the first main proxy server and the second standby proxy server can be removed from a routing table, and at the moment, only the routing information of the first standby proxy server and the second main proxy server which can still work normally at present is recorded in the routing table.
When the producer needs to issue the message, the producer will first access the route discovery server to pull the route information of the proxy server in the system. The process of the producer accessing the route discovery server may be random access, that is, randomly selecting one from the first route discovery server and the second route discovery server, if the route information can be pulled, then using the pulled route information to issue the message, and if the route information is not pulled, then selecting another route discovery server in the system to access until the route information is pulled.
After the first main proxy server and the second standby proxy server fail, the second route discovery server rejects the first main proxy server and the second standby proxy server from the route table, so that the route information of the first main proxy server and the second standby proxy server in the route information pulled by the producer is invisible, and then the producer can issue the message by using the second main proxy server visible in the route information, thereby ensuring that the consumption of normal messages is not interrupted and no message is lost.
For the producer, the second main proxy server exists in the system, so that the message can be normally issued. For the consumer, the message can be pulled normally from the second master proxy server.
According to the embodiment of the invention, the first standby proxy server monitors the fault condition of the first main proxy server by the following operations:
the method comprises the steps that a routing table is obtained from a route discovery server, wherein the routing table is used for recording heartbeat information of a first main proxy server, and deleting the heartbeat information of the first main proxy server from the routing table after the heartbeat from the first main proxy server is not received within preset time;
and under the condition that the heartbeat information of the first main proxy server does not exist in the routing table, determining that the first main proxy server fails.
According to the embodiment of the invention, the first standby proxy server can periodically acquire the routing table from the route discovery server and confirm whether the route discovery server rejects the first main proxy server from the routing table, if the route discovery server rejects the first main proxy server from the routing table, the first standby proxy server indicates that the first main proxy server has heartbeat disconnection, namely the first main proxy server has faults, so that the first standby proxy server can execute the operation of scanning target messages meeting the delivery requirements in the first main proxy server. If the heartbeat information of the first main proxy server exists in the routing table, the first main proxy server is in a normal working state, and the first standby proxy server only needs to receive and store the data synchronized by the first main proxy server.
According to the embodiment of the invention, the working state of the first main proxy server can be determined by acquiring the routing table from the route discovery server and inquiring the routing table, and an additional communication link with the first main proxy server is not required to be established, so that the complexity of state monitoring in the working process of the first main proxy server is simplified.
According to the embodiment of the invention, the routing table is also used for recording the heartbeat information of the second main proxy server;
according to the embodiment of the invention, the sending of the target message to the second main proxy server deployed in the same physical machine as the first standby proxy server may be specifically implemented as follows:
determining whether heartbeat information of the second main proxy server exists in the routing table;
and under the condition that the heartbeat information of the second main proxy server exists in the routing table, the target message is sent to the second main proxy server.
According to the embodiment of the invention, the working state of the second main proxy server can be determined by determining whether the heartbeat information of the second main proxy server exists in the routing table, if the heartbeat information of the second main proxy server exists in the routing table, the second main proxy server is indicated to be in a normal working state, and no fault occurs, at this time, the target message can be sent to the second main proxy server, so that the consumer can pull the target message from the message queue of the second main proxy server.
If the heartbeat information of the second main proxy server does not exist in the routing table, the heartbeat disconnection of the second main proxy server is indicated, namely the second main proxy server fails, at this time, the first standby proxy server can determine another main proxy server, such as a third main proxy server, from the routing table, and send the target message to the third main proxy server. The third primary proxy server may be a primary proxy server deployed in the same machine room as the first backup proxy server.
According to the embodiment of the invention, the scanning of the target message meeting the delivery requirement in the first main proxy server side can be specifically realized as follows:
traversing the message to be processed stored in the message storage component of the first main proxy server;
and determining the message to be processed meeting the putting requirements as a target message.
According to the embodiment of the invention, the first main proxy server side can traverse the information to be processed in the special Topic in the scanning message storage component by using the scanning thread.
According to the embodiment of the invention, the first standby proxy server can temporarily not process the information to be processed which does not meet the release requirement until the information to be processed meets the release requirement.
According to the embodiment of the invention, for example, the message A, the message B and the message C are stored in the special Topic of the message storage component of the first main proxy server, when the first standby proxy server scans the special Topic of the message storage component of the first main proxy server by using the scanning thread at the first moment, the message A and the message B do not meet the release requirement, and the message C meets the release requirement, then the message C can be pulled and sent to the second main proxy server, and the message C is successfully consumed.
After the message C is successfully consumed, the special Topic of the message storage component of the first main proxy server also stores the message A and the message B. At the second moment, the first standby proxy server can query the routing table again to determine whether the first main proxy server resumes the online, and if the first main proxy server is not online, the first standby proxy server can start the scanning thread again to scan the special Topic of the message storage component of the first main proxy server at the second moment, and pull the message meeting the delivery requirement at the second moment.
According to an embodiment of the invention, in case the message to be processed comprises a timing message, the drop requirement comprises:
The timing message reaches the preset delivery time;
in the case where the pending message comprises a transaction message, the drop requirement comprises:
acknowledgement information for the transaction message is obtained.
Fig. 4 is a flowchart of an embodiment of a message processing method according to another embodiment of the present invention, where the method may be applied to a distributed message system, and the method may include the following steps:
401, under the condition that the first main proxy server resumes working, the first main proxy server acquires the address of the first standby proxy server from the route discovery server;
402, the first main proxy server establishes communication connection with the first standby proxy server through the address;
403, the first main proxy server obtains metadata sent by the first standby proxy server through communication connection, so that the first main proxy server determines whether to update metadata according to the version number of the metadata, wherein the version number of the metadata is determined according to the consumption number of target messages under the condition that the first main proxy server fails, and the target messages comprise messages which are pulled from the first main proxy server by the first standby proxy server and sent to the second main proxy server.
According to the embodiment of the present invention, the specific flow of the first backup proxy server pulling from the first main proxy server and sending to the second main proxy server is the same as or similar to the operation of the message processing method shown in fig. 2, and the embodiment of the present invention is not described herein again.
Fig. 5 schematically shows a schematic diagram of a message processing method in the case where the first main proxy server resumes operation.
As shown in fig. 5, after the fault of the first main proxy server 501 is repaired, the route discovery server 502 may be accessed first to obtain the address of the first standby proxy server 502, but the first main proxy server 501 is not registered in the route discovery server 502 at this time, that is, the first main proxy server 501 is temporarily and formally online and is invisible to the outside.
After the first main proxy server 501 obtains the address of the first standby proxy server 502, the address of the first main proxy server 501 may be sent to the first standby proxy server 502.
After the first backup proxy server 502 receives the address of the first main proxy server 501, a communication connection can be established with the first main proxy server 501, handshake is completed, and metadata of the first backup proxy server 502 is sent to the first main proxy server 501 based on the established communication connection.
According to embodiments of the present invention, metadata may include data of consumption sites, timing message progress, etc.
According to the embodiment of the invention, after the first main proxy server 501 fails, the first standby proxy server 502 proxies the first main proxy server 501 to store and deliver the target message, so that the main standby relationship of the proxy server of the RocketMQ system is not changed. Because of the readable and non-writable nature of the first backup proxy server 502, after the first primary proxy server 501 is restored, the CommitLog of each of the first backup proxy server 502 and the first primary proxy server 501 has data consistency.
However, since the first proxy agent 501 takes on the role of standby reading and proxies the target message after the first proxy agent 502 goes offline, part of the metadata in the first proxy agent 502 may be more advanced than the metadata of the first proxy agent 501. In the related art, if the first main proxy server 501 resumes online, the metadata is updated based on its own metadata, that is, metadata synchronization is performed with the first standby proxy server 502, which may cause the metadata of the proxy server to rollback, resulting in repeated consumption of a large amount of messages.
In the embodiment of the present invention, after the first main proxy server 501 is online, the metadata of the first backup proxy server 502 is reversely acquired by the first main proxy server 502, and whether to update is determined based on the version number of the received metadata of the first backup proxy server 502, so that the technical problem that a large number of messages are repeatedly consumed due to metadata rollback in the related art can be solved.
In an embodiment of the invention, the concept of a version number is innovatively added to metadata, and in order to prevent version number updating too often, a concept of a step size is also proposed, for example, for a consumption site, the version number of the consumption site may be updated to the next version 500 times per update of the consumption site. It should be noted that, the update step of the version number may be flexibly set by a person skilled in the art according to the actual application requirement, for example, may be 300, 400, 700, 1000, etc.
In a specific example, before the first main proxy server fails, the version number of the consumption site is 2.1.1, and correspondingly, the version number of the consumption site of the first standby proxy server is also 2.1.1. In the process from the disconnection of the first main proxy server to the disconnection of the repair fault and the disconnection of the first main proxy server again, the version number of the consumption site of the standby proxy server is updated to 2.1.2 due to the target message proxy operation of the first standby proxy server, namely, the first standby proxy server takes 500 target messages for the first main proxy server in the time from the disconnection of the first main proxy server to the disconnection of the repair fault and the disconnection of the first main proxy server. In this case, if the metadata of the first backup proxy server is still synchronized by using the consumption site with version number 2.1.1 after the first main proxy server resumes online, it may result in repeated consumption of the 500-item label message that has already been consumed.
In the embodiment of the invention, after the first main proxy server resumes the online, the first main proxy server can reversely acquire the metadata of the first standby proxy server, and by combining the above example, after the first main proxy server acquires the metadata of the first standby proxy server, it is determined that the version number of the metadata of the first standby proxy server has been updated, so that the first main proxy server can correspondingly update its consumption site to 2.1.2, thereby avoiding repeated consumption of messages.
According to the embodiment of the invention, after the metadata of the first backup proxy server is reversely acquired, if the version number of the metadata of the first backup proxy server is the same as the version number of the first main proxy server, the fact that the first backup proxy server does not proxy the first main proxy server to consume the target message during the failure period of the first main proxy server is indicated, and at the moment, the metadata of the first backup proxy server can be covered by the metadata of the first main proxy server.
Fig. 6 is a flowchart of another embodiment of a message processing method, which may be applied to a second master proxy server of a distributed message system, and the method may include the following steps:
601, acquiring a target message sent by a first standby proxy server; the target message is obtained by scanning the first main proxy server under the condition that the first main proxy server fails;
and 602, storing the target message into a message queue for consumers to consume the target message from the message queue.
Fig. 7 is a schematic diagram of a message processing system according to an embodiment of the present invention, where a message processing system 700 includes a first main proxy server 701, a second main proxy server 702, and a first standby proxy server 703 corresponding to the first main proxy server 701; wherein, the first standby proxy server 703 and the second main proxy server 702 are respectively located in different areas with the first main proxy server 701;
the first proxy server 703 is configured to:
under the condition that the first main proxy server 701 fails, scanning target messages meeting the delivery requirements in the first main proxy server 701;
the target message is sent to a second main proxy server 702 deployed in the same physical machine as the first standby proxy server 703; the target message is stored in the message queue of the second home agent server 702 for consumption by the consumer.
In accordance with an embodiment of the present invention, the message processing system 700 further includes a second backup proxy server 704 corresponding to the second primary proxy server 702. It should be noted that, the second proxy server 704 is not limited to be disposed in the area a, but may be disposed in an area C different from the area B.
According to an embodiment of the present invention, each of the regions A and B in the message processing system 700 includes a NameServer.
According to some embodiments of the invention, each proxy server may be deployed separately in a physical machine.
According to the preferred embodiment of the invention, a mixed deployment of the primary and the backup can be further realized in each physical machine, namely, at least one primary proxy server and at least one backup proxy server can be deployed in one physical machine.
According to the embodiment of the invention, the first standby proxy server and the second main proxy server are deployed in the same physical machine in the same area.
According to the embodiment of the invention, by carrying out the primary-backup mixed deployment in each physical machine, the internal flow circulation of the backup proxy server side when the target message is sent can be saved, and the utilization rate of network resources can be improved.
Fig. 8 is a block diagram of a first backup proxy server provided in an embodiment of the present invention, where the first backup proxy server 800 includes a scanning module 801 and a sending module 802.
A scanning module 801, configured to scan, in case of a failure of the first primary proxy server, a target message in the first primary proxy server that meets a delivery requirement;
a sending module 802, configured to send the target message to the second main proxy server; the target message is stored in a message queue of the second main proxy server for the consumer to consume the target message.
According to an embodiment of the present invention, the scanning module 801 includes a start-up unit and a scanning unit.
The starting unit is used for starting a scanning thread corresponding to the first main proxy server under the condition that the first main proxy server is monitored to be faulty;
and the scanning unit is used for scanning the message storage component of the first main proxy server by utilizing the scanning thread so as to acquire the target message from the message storage component.
According to an embodiment of the present invention, the first proxy server 800 further includes an acquisition module and a fault determination module.
The acquisition module is used for acquiring a routing table from the route discovery server, wherein the routing table is used for recording the heartbeat information of the first main proxy server and deleting the heartbeat information of the first main proxy server from the routing table after the heartbeat from the first main proxy server is not received within a preset time;
The fault determining module is used for determining the fault of the first main proxy server under the condition that the heartbeat information of the first main proxy server does not exist in the routing table.
According to the embodiment of the invention, the routing table is further used for recording heartbeat information of the second main proxy server side.
According to an embodiment of the present invention, the transmitting module 802 includes a heartbeat acknowledgment unit, a transmitting unit.
The heartbeat confirming unit is used for determining whether heartbeat information of the second main proxy server exists in the routing table;
and the sending unit is used for sending the target message to the second main proxy server side under the condition that the heartbeat information of the second main proxy server side exists in the routing table.
According to an embodiment of the invention, in case the message to be processed comprises a timing message, the drop requirement comprises:
the timing message reaches the preset delivery time;
in the case where the pending message comprises a transaction message, the drop requirement comprises:
acknowledgement information for the transaction message is obtained.
Fig. 9 is a block diagram of a second main proxy server provided in an embodiment of the present invention, where the second main proxy server 900 includes:
a target message obtaining module 901, configured to obtain a target message sent by a first backup proxy server, where the target message is obtained by scanning a first backup proxy server from the first main proxy server under a condition that the first main proxy server fails;
A storage module 902, configured to store the target message in a message queue, so that a consumer consumes the target message from the message queue.
Fig. 10 is a block diagram of a first primary proxy server provided in an embodiment of the present invention, where the first primary proxy server 1000 includes:
an address obtaining module 1001, configured to obtain, from a route discovery server, an address of a first backup proxy server when the first master proxy server resumes operation;
a connection establishment module 1002, configured to establish a communication connection with the first proxy server based on the address;
the metadata obtaining module 1003 is configured to obtain metadata sent by the first backup proxy server through the communication connection, so that the first primary proxy server determines whether to update metadata according to a version number of the metadata, where the version number of the metadata is determined according to a consumption number of a target message under a condition that the first primary proxy server fails, and the target message includes a message that the first backup proxy server pulls from the first primary proxy server and sends to a second primary proxy server.
The first proxy server in fig. 8 may execute the message processing method in the embodiment shown in fig. 2, and its implementation principle and technical effects are not repeated. The specific manner in which the individual modules, units, and operations of the apparatus 8 in the above embodiments are described in detail in connection with the embodiments of the method will not be described in detail here.
In one possible design, the first standby proxy server or the second main proxy server of the embodiment shown in fig. 8 may be implemented as a computing device, which may include a storage component 1101 and a processing component 1102, as shown in fig. 11;
the storage component 1101 stores one or more computer instructions for execution by the processing component 1102 for implementing the message processing method as illustrated in fig. 2.
Of course, the computing device may necessarily include other components, such as input/output interfaces, communication components, and the like. The input/output interface provides an interface between the processing component and a peripheral interface module, which may be an output device, an input device, etc. The communication component is configured to facilitate wired or wireless communication between the computing device and other devices, and the like.
The computing device may be a physical device or an elastic computing host provided by the cloud computing platform, and at this time, the computing device may be a cloud server, and the processing component, the storage component, and the like may be a base server resource rented or purchased from the cloud computing platform.
When the computing device is a physical device, the computing device may be implemented as a distributed cluster formed by a plurality of servers or terminal devices, or may be implemented as a single server or a single terminal device.
In practical application, the computing device may be specifically deployed to a node in the distributed message system, and implemented as a proxy server in the distributed message system, and the like.
The embodiment of the invention also provides a computer readable storage medium, which stores a computer program, and the computer program can implement the message processing method of the embodiment shown in fig. 2 when being executed by a computer.
The embodiment of the invention also provides a computer program product, which comprises a computer program, and the computer program can realize the message processing method of the embodiment shown in the figure 2 when being executed by a computer.
Wherein the processing components of the respective embodiments above may include one or more processors to execute computer instructions to perform all or part of the steps of the methods described above. Of course, the processing component may also be implemented as one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic elements for executing the methods described above.
The storage component is configured to store various types of data to support operation in the device. The memory component may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
The apparatus embodiments described above are merely illustrative, wherein elements illustrated as separate elements may or may not be physically separate, and elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on such understanding, the foregoing technical solutions may be embodied essentially or in part in the form of a software product, which may be stored in a computer-readable storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the various embodiments or methods of some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (10)
1. A message processing method for use in a distributed messaging system, the method comprising:
under the condition that a first main proxy server fails, a first standby proxy server scans target messages meeting the delivery requirements in the first main proxy server;
the target message is sent to a second main proxy server; the target message is stored in a message queue of the second main proxy server for consumers to consume.
2. The method of claim 1, wherein the first backup proxy server scanning for target messages meeting delivery requirements in a first primary proxy server in the event of a failure of the first primary proxy server comprises:
Under the condition that the first main proxy server side fault is monitored, starting a scanning thread corresponding to the first main proxy server side;
and scanning a message storage component of the first main proxy server by using the scanning thread so as to acquire the target message from the message storage component.
3. The method according to claim 1 or 2, wherein a first backup proxy server monitors the fault condition of the first primary proxy server by:
obtaining a routing table from a route discovery server, wherein the routing table is used for recording heartbeat information of the first main proxy server, and deleting the heartbeat information of the first main proxy server from the routing table after the heartbeat information of the first main proxy server is not received in preset time;
and determining that the first main proxy server fails under the condition that the heartbeat information of the first main proxy server does not exist in the routing table.
4. The method of claim 3, wherein the routing table is further configured to record heartbeat information of the second primary proxy server;
the sending the target message to a second main proxy server deployed in the same physical machine as the first standby proxy server includes:
Determining whether heartbeat information of the second main proxy server exists in the routing table;
and sending the target message to the second main proxy server under the condition that the heartbeat information of the second main proxy server exists in the routing table.
5. The method of claim 1, wherein the second primary proxy server is deployed in the same physical machine as the first backup proxy server.
6. The method of claim 5, wherein the step of determining the position of the probe is performed,
in case the pending message comprises a timing message, the drop requirement comprises:
the timing message reaches a preset delivery time;
in case the pending message comprises a transaction message, the drop requirement comprises:
acknowledgement information for the transaction message is obtained.
7. A message processing method for use in a distributed messaging system, the method comprising:
under the condition that the first main proxy server resumes work, the first main proxy server acquires the address of the first standby proxy server from the route discovery server;
the first main proxy server establishes communication connection with the first standby proxy server based on the address;
The first main proxy server acquires metadata sent by the first standby proxy server through the communication connection, so that the first main proxy server determines whether to update metadata according to the version number of the metadata, wherein the version number of the metadata is determined according to the consumption number of target messages under the condition that the first main proxy server fails, and the target messages comprise messages which are pulled from the first main proxy server by the first standby proxy server and are sent to the second main proxy server.
8. A message processing method, which is characterized by being applied to a second main proxy server of a distributed message system; the method comprises the following steps:
acquiring a target message sent by a first standby proxy server; the target message is obtained by scanning a first standby proxy server from the first main proxy server under the condition that the first main proxy server fails;
storing the target message in a message queue for consumers to consume the target message from the message queue.
9. A computing device comprising a processing component and a storage component;
the processing component is used for running the first standby proxy server and/or the second main proxy server;
The storage component stores one or more computer instructions; the one or more computer instructions are to be invoked for execution by the processing component to implement the message processing method of any one of claims 1-6 and/or the message processing method of claim 7 and/or the message processing method of claim 8.
10. A computer storage medium, characterized in that a computer program is stored, which, when being executed by a computer, implements the message processing method according to any one of claims 1-6 and/or the message processing method according to claim 7 and/or the message processing method according to claim 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210141634.3A CN114598593B (en) | 2022-02-16 | 2022-02-16 | Message processing method, system, computing device and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210141634.3A CN114598593B (en) | 2022-02-16 | 2022-02-16 | Message processing method, system, computing device and computer storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114598593A CN114598593A (en) | 2022-06-07 |
| CN114598593B true CN114598593B (en) | 2023-08-29 |
Family
ID=81805448
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210141634.3A Active CN114598593B (en) | 2022-02-16 | 2022-02-16 | Message processing method, system, computing device and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114598593B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114827278B (en) * | 2022-06-24 | 2022-09-02 | 小米汽车科技有限公司 | Task scheduling method, system, device and equipment based on message queue |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106953901A (en) * | 2017-03-10 | 2017-07-14 | 重庆邮电大学 | A kind of trunked communication system and its method for improving message transmission performance |
| CN107197015A (en) * | 2017-05-23 | 2017-09-22 | 阿里巴巴集团控股有限公司 | A kind of message treatment method and device based on Message Queuing system |
| CN108306941A (en) * | 2018-01-05 | 2018-07-20 | 上海你我贷互联网金融信息服务有限公司 | A kind of distributed information system |
| CN110601903A (en) * | 2019-09-25 | 2019-12-20 | 广州荔支网络技术有限公司 | Data processing method and device based on message queue middleware |
| CN112597249A (en) * | 2020-12-26 | 2021-04-02 | 湖南快乐阳光互动娱乐传媒有限公司 | Synchronous distribution and storage method and system for service data |
| CN113641511A (en) * | 2021-07-09 | 2021-11-12 | 阿里云计算有限公司 | Message communication method and device |
| CN113849320A (en) * | 2021-08-20 | 2021-12-28 | 阿里巴巴新加坡控股有限公司 | Development method, control method and computing device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11064022B2 (en) * | 2019-01-29 | 2021-07-13 | Verizon Patent And Licensing Inc. | Messaging system failover |
| US11347594B2 (en) * | 2019-11-26 | 2022-05-31 | International Business Machines Corporation | Inter-processor communications fault handling in high performance computing networks |
-
2022
- 2022-02-16 CN CN202210141634.3A patent/CN114598593B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106953901A (en) * | 2017-03-10 | 2017-07-14 | 重庆邮电大学 | A kind of trunked communication system and its method for improving message transmission performance |
| CN107197015A (en) * | 2017-05-23 | 2017-09-22 | 阿里巴巴集团控股有限公司 | A kind of message treatment method and device based on Message Queuing system |
| CN108306941A (en) * | 2018-01-05 | 2018-07-20 | 上海你我贷互联网金融信息服务有限公司 | A kind of distributed information system |
| CN110601903A (en) * | 2019-09-25 | 2019-12-20 | 广州荔支网络技术有限公司 | Data processing method and device based on message queue middleware |
| CN112597249A (en) * | 2020-12-26 | 2021-04-02 | 湖南快乐阳光互动娱乐传媒有限公司 | Synchronous distribution and storage method and system for service data |
| CN113641511A (en) * | 2021-07-09 | 2021-11-12 | 阿里云计算有限公司 | Message communication method and device |
| CN113849320A (en) * | 2021-08-20 | 2021-12-28 | 阿里巴巴新加坡控股有限公司 | Development method, control method and computing device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114598593A (en) | 2022-06-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2902922B1 (en) | Distributed file system and data backup method for distributed file system | |
| CN102394914A (en) | Cluster brain-split processing method and device | |
| JP2002522845A (en) | Fault tolerant computer system | |
| CN113641511A (en) | Message communication method and device | |
| JP2012528382A (en) | Cache data processing using cache clusters in configurable mode | |
| JPS61500751A (en) | Method for stopping program processes in multiprocessing systems | |
| CN110677282B (en) | Hot backup method of distributed system and distributed system | |
| US20210136145A1 (en) | Method for Changing Member in Distributed System and Distributed System | |
| CN109766194B (en) | Method and system for realizing low-coupling plan task component based on message | |
| CN108173971A (en) | A kind of MooseFS high availability methods and system based on active-standby switch | |
| CN104077181A (en) | Status consistent maintaining method applicable to distributed task management system | |
| US20100268687A1 (en) | Node system, server switching method, server apparatus, and data takeover method | |
| CN104158707A (en) | Method and device of detecting and processing brain split in cluster | |
| CN114598593B (en) | Message processing method, system, computing device and computer storage medium | |
| JPH08212095A (en) | Client server control system | |
| CN114124650A (en) | Master-slave deployment method of SPTN (shortest Path bridging) network controller | |
| CN110971662A (en) | Two-node high-availability implementation method and device based on Ceph | |
| CN111726388A (en) | Cross-cluster high-availability implementation method, device, system and equipment | |
| CN114265753A (en) | Management method and management system of message queue and electronic equipment | |
| CN105323271B (en) | Cloud computing system and processing method and device thereof | |
| CN112052127B (en) | Data synchronization method and device for dual-computer hot standby environment | |
| CN113055203B (en) | Method and device for recovering exception of SDN control plane | |
| CN116185697B (en) | Container cluster management method, device and system, electronic equipment and storage medium | |
| CN110351122B (en) | Disaster recovery method, device, system and electronic equipment | |
| CN114422335A (en) | Communication method, communication device, server and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |