WO2023280127A1

WO2023280127A1 - Message communication method and apparatus

Info

Publication number: WO2023280127A1
Application number: PCT/CN2022/103745
Authority: WO
Inventors: 聂诗超; 周新宇; 林清山
Original assignee: 阿里云计算有限公司
Priority date: 2021-07-09
Filing date: 2022-07-04
Publication date: 2023-01-12
Also published as: CN113641511A

Abstract

The present application provides a message communication method and apparatus. The method comprises: after receiving a message sent by a producer, a master broker server at a node synchronizes the message with a slave broker server of at least one other node; and the master broker server sends the message to a consumer, or the slave server of the other node sends the message to the consumer. By providing a novel high-availability message queue architecture in which each node comprises a master broker server and at least one slave broker server, for a single node to contain a plurality of Brokers is implemented, the utilization rates of the nodes in a message broker service cluster are improved, and the waste of node resources is reduced; because each node comprises a master broker server, it can be ensured that the capabilities of the nodes are equivalent; and by means of the message synchronization of the master and slave broker servers between different nodes, on the premise of ensuring the message consistency of the nodes, a non-master-selection process performed when the node message is transmitted, and in particular, when the node fails can be implemented.

Description

A message communication method and device

This application claims the priority of the Chinese patent application with the application number 202110781013.7 and the application name "A Message Communication Method and Device" submitted to the China Patent Office on July 09, 2021, the entire contents of which are incorporated by reference in this application .

technical field

The present application relates to the technical field of communication, and in particular to a message communication method and a message communication device.

Background technique

A distributed system (Distributed System) is a software system built on the network. For users, it can be equivalent to a single related system, but in fact it is a collection of several independent computers. Among them, the independent computers used to form the system It can be geographically dispersed, and the functions of the entire system can be realized by dispersing on each node.

Message queue middleware (such as Rocket MQ (Rocket Message Queue, refers to an open source message middleware), ONS (Open Notification Service, open message service, based on the open source message middleware Rocket MQ), Kafka (an Open source distributed high-concurrency message middleware) etc.) are important components in distributed systems, which are mainly used to solve the problem of message transmission between distributed systems. Message broker is an architecture for message verification, transformation, and routing Although different message middleware architectures and implementations are different, most of them implement Broker, which is a proxy server in the message system and can have the logic of sending and receiving messages with message producers and message consumers. In the currently implemented middleware architecture, each Broker monopolizes a message proxy service. When the Broker is running normally, the standby proxy server only needs to synchronize messages from the main proxy server, and its resource utilization is at a low level most of the time. This leads to a certain degree of waste of resources.

Contents of the invention

In view of the above problems, the embodiments of the present application are proposed to provide a message communication method and a corresponding message communication device that overcome the above problems or at least partially solve the above problems.

The embodiment of the present application discloses a message communication method, which is applied to a message system. The message system includes a producer, a message broker service cluster, and a consumer. The message broker service cluster includes multiple nodes, and each node includes a Replicas, and including a master proxy server and at least one secondary proxy server belonging to different replica groups, the method includes:

After the main proxy server of a node receives the message sent by the producer, it synchronizes the message with the secondary proxy server of at least one other node;

The primary proxy server sends messages to consumers, or another node's secondary server sends messages to consumers.

Optionally, message synchronization with the sub-proxy server of at least one other node includes:

Synchronize messages with at least one secondary proxy server belonging to the same copy group as the primary proxy server; wherein, each secondary proxy server belonging to the same copy group and the primary proxy server are located at different nodes.

Optionally, synchronizing the message sent by the producer to at least one secondary proxy server belonging to the same replica group as the primary proxy server includes:

Configure the number of proxy servers for message synchronization with the main proxy server;

According to the configured number of proxy servers, the messages sent by the producer are synchronized to the proxy servers belonging to the same replica group.

Optionally, the method also includes:

The secondary proxy server of another node synchronizes the current metadata with the primary proxy server.

Optionally, the secondary proxy server of another node synchronizes the current metadata with the primary proxy server, including:

Through a secondary proxy server belonging to the same copy group as the primary proxy server, after the fault of the primary proxy server is repaired, the current metadata is synchronized to the primary proxy server.

Optionally, the secondary server of another node sends a message to the consumer, including:

The secondary proxy server of another node sends a message to the consumer when the primary proxy server fails.

Optionally, the sub-proxy server of another node sends a message to the consumer, including:

Messages are sent to consumers through a secondary proxy that belongs to the same replica group as the primary proxy.

The embodiment of the present application also discloses a message communication device, which is applied to a message system. The message system includes a producer, a message broker service cluster, and a consumer. The message broker service cluster includes multiple nodes, and each node includes A replica, and includes a primary proxy server and at least one sub-proxy server belonging to different replica groups, the device includes:

The message synchronization module is located at the main proxy server of one node, and is used to perform message synchronization with the secondary proxy server of at least one other node after receiving the message sent by the producer;

The first message sending module is located at the main proxy server and is used to send messages to consumers;

The second message sending module is located in the secondary server of another node, and is used to send messages to consumers.

Optionally, the message synchronization module includes:

The message synchronization sub-module is used to synchronize messages with at least one sub-proxy server belonging to the same copy group as the main proxy server; wherein, the sub-proxy servers and the main proxy server belonging to the same copy group are located at different nodes.

Optionally, the message synchronization submodule includes:

The proxy server quantity configuration unit is used to configure the proxy server quantity for message synchronization with the main proxy server;

The message synchronization unit is used to synchronize the messages sent by the producer to the proxy servers belonging to the same copy group according to the configured number of proxy servers.

Optionally, the device includes:

The metadata reverse synchronization module is located in the secondary proxy server of another node, and is used to synchronize the current metadata with the primary proxy server.

Optionally, the metadata reverse synchronization module includes:

The metadata reverse synchronization sub-module is used for synchronizing the current metadata with the primary proxy server after the failure of the primary proxy server is repaired through a secondary proxy server belonging to the same replica group as the primary proxy server.

Optionally, the second message sending module includes:

The message sending sub-module is located in the secondary proxy server of another node, and is used to send messages to consumers when the primary proxy server fails.

The embodiment of the present application also discloses an electronic device, including: a processor, a memory, and a computer program stored on the memory and capable of running on the processor. When the computer program is executed by the processor, the steps of any message communication method are implemented. .

The embodiment of the present application also discloses a computer-readable storage medium. A computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, the steps of any message communication method are implemented.

The embodiment of the present application also discloses a computer program. When the computer program is executed by a processor, the electronic device is made to execute the steps of any message communication method.

The embodiment of the present application includes the following advantages:

In the embodiment of this application, a message processing method applied to a message system is proposed, mainly through the nodes of the message broker service cluster to realize message transmission with producers and consumers, wherein each node in the message broker service cluster can It includes a copy of each copy group, and includes a primary proxy server and at least one secondary proxy server belonging to different copy groups. After the primary proxy server of a node receives the message sent by the producer, it can communicate with at least one other node. The secondary proxy server performs message synchronization, and its primary proxy server or another node's secondary proxy server can send messages to consumers. By proposing a new message queue high-availability architecture with each node including a primary proxy server and at least one sub-proxy server, it realizes multiple Brokers on a single point, improves the utilization rate of nodes in the message proxy service cluster, and reduces the waste of node resources; and because each Each node includes a primary proxy server, which can ensure that the capabilities of each node are equal, and through the message synchronization of the primary and secondary proxy servers between different nodes, it can realize node message transmission under the premise of ensuring the consistency of each node message , especially the no-election master process in case of node failure.

Description of drawings

1A to 1C are schematic diagrams of the structure of the message queue middleware in the related art;

Fig. 2 is a schematic diagram of the architecture of the message queue middleware in the embodiment of the present application;

Fig. 3 is a flow chart of the steps of an embodiment of a message communication method of the present application;

FIG. 4 is a flowchart of steps of another message communication method embodiment of the present application;

Fig. 5 is a schematic diagram of the process of data synchronization in the embodiment of the present application;

FIG. 6 is an application scenario diagram of a message communication method in an embodiment of the present application;

FIG. 7 is a flow chart of the steps of another message communication method embodiment of the present application;

FIG. 8 is an application scenario diagram of another message communication in the embodiment of the present application;

FIG. 9 is a schematic diagram of the process of metadata reverse synchronization in the embodiment of the present application;

Fig. 10 is a schematic framework diagram of the message communication system in the embodiment of the present application;

Fig. 11 is a structural block diagram of an embodiment of a message communication device of the present application.

detailed description

In order to make the above objects, features and advantages of the present application more obvious and comprehensible, the present application will be further described in detail below in conjunction with the accompanying drawings and specific implementation methods.

In order to facilitate those skilled in the art to further understand the message processing method proposed in this application, the terms or nouns involved in the following embodiments of this application are explained below:

Topic: Topic is an abstract classification of a group of messages. Producers can publish messages through Topic, and consumers can subscribe to messages through Topic to realize message transmission;

Message: can refer to the combination of messages and (optional) attributes sent by the producer to the Topic and finally delivered to the consumer;

Producer: The producer and/or sender of the message, that is, the sender of the message, which can be a single server or a server cluster;

Consumer: The consumer of the message, that is, the requesting party, which can also be a single server or a server cluster;

Broker: The proxy server in the message system (that is, the message middleware server), which can have a message sending and consuming interface externally, and message producers and consumers can interact with it to complete the core message sending and receiving logic;

Master/Leader Broker: The main proxy server, which undertakes the function of providing external services under normal circumstances;

Slave/Follower Broker: The secondary proxy server is actually a copy of the primary proxy server. It can have all the messages on the primary proxy server and can provide external services when the primary proxy server is offline;

Commit Log: The message storage component of the message queue middleware, which is used to save all the messages received by the message queue middleware;

Metadata: Messages used to record consumption and sending status in the message queue middleware, such as consumption location, timing message playback location, etc.

Message queuing middleware (such as Rocket MQ, ONS, Kafka, etc.) is an important component in a distributed system, which is mainly used to solve the problem of message delivery between distributed systems. Referring to Figures 1A to 1C, it shows Schematic diagram of the architecture of the message queue middleware, which mainly relates to the communication architecture adopted by the Broker cluster (that is, the message broker service cluster) in the message system. Among them, M is used to represent the master proxy server Master Broker, and S is used to represent the secondary proxy server Slave Broker.

As shown in Figure 1A, the communication architecture adopted by the Broker cluster is an active-standby architecture, which only supports one active and one standby, and can support multiple message replication modes to achieve message synchronization, but it adopts cold standby (standby unreadable) Deployment method, that is, the secondary proxy server is only used to synchronize the messages of the primary proxy server, but cannot provide external read and write services; and when the Master Broker fails, it needs to manually switch between the active and standby, and there are relatively large resources in large-scale scenarios. waste and operating costs.

As shown in Figure 1B, the communication architecture adopted by the Broker cluster is an active-standby architecture based on ZK (Zoo Keeper, distributed coordination kernel), which can support one master and multiple backups, but the deployment method adopted is also cold standby (standby Unreadable) mode, that is, the secondary proxy server is only used to synchronize the messages of the primary proxy server, but cannot provide external read and write services; it can coordinate services based on an additional Zoo Keeper cluster, realize the function of automatically selecting the master, and support the emergence of Master Broker In the event of a failure, the Slave is automatically switched to the Master to provide services, but the failover takes a long time, and it takes about 10 seconds to complete the master selection.

As shown in Figure 1C, the communication architecture adopted by the Broker cluster is the Leader-Follower architecture based on the Raft protocol (referring to the distributed consensus protocol), which can support one master and multiple backups, and can be based on the Follower provided by the Raft protocol. (i.e. the secondary proxy server Slave Broker) is redirected to the Leader (i.e. the main proxy server Master Broker) to achieve automatic master selection without relying on additional Zoo Keeper clusters, but due to failures still need to wait for the master election, the entire failover time is longer, However, the strongly consistent Raft protocol does not yet support a dynamic downgrade strategy, making it impossible to flexibly balance availability and reliability.

In the above three message queuing middleware architectures, each Broker will monopolize a node in the message broker service cluster, and in the copy group (referring to a group of Brokers with the same message, usually composed of one master and N standby) In the normal working state, the node where the Master Broker is located undertakes all read and write services, while the node where the Slave Broker is located does not have read and write services, and only needs to synchronize messages from the Master Broker, so that the resource utilization rate of the node where the Slave Broker is located is at most of the time. A lower level leads to a certain degree of waste of node resources.

One of the core ideas of the embodiment of the present application is to propose a new message queue high-availability architecture in which each node includes a copy of each copy group, and includes a primary proxy server and at least one secondary proxy server belonging to different copy groups, so that Any node in the message broker service cluster can have the full amount of data of the cluster, realize single-point multi-Broker, improve the utilization rate of nodes in the message broker service cluster, and reduce the waste of node resources; and because each node includes a master The proxy server can ensure that the capabilities of each node are equal (both have read and write services), and through the message synchronization of the primary and secondary proxy servers between different nodes, the node message can be realized under the premise of ensuring the consistency of each node message. When transmitting, especially in the case of node failure, there is no master election process.

In the embodiment of this application, in order to improve the utilization rate of the nodes in the message proxy server cluster, the communication architecture of the message queue middleware adopted by the message proxy service cluster can be processed at this time. Specifically, each node in the message proxy service cluster can Nodes are configured with a primary proxy server and a secondary proxy server at the same time. For example, each node can include a primary proxy server and at least one secondary proxy server to achieve single-point multi-Broker and reduce node resource waste.

Specifically, referring to FIG. 2 , it shows a schematic diagram of the architecture of the message queue middleware in the embodiment of the present application. The message broker service cluster using the message queue middleware architecture may include multiple nodes, such as node 1, node 2 and node 3 , each node can include multiple Brokers. For a message broker service cluster with 3 masters and 6 backups, each Broker in the existing high-availability architecture will exclusively occupy one node, and nine nodes are required to complete the deployment. Only 3 nodes are needed to complete the deployment, reducing the loss of node resources.

In practical applications, each node can add or delete Broker through Broker Container (for Broker management process), and manage network request distribution and resource scheduling of all Brokers in the process. The added Broker can provide read and write services The main proxy server Master Broker, and the secondary proxy server Slave Broker that only provides read services. In the embodiment of this application, a Broker Container corresponds to manage a node, and each node can include a primary proxy server and at least one secondary proxy server. And the included proxy servers do not belong to the same copy group, that is, the messages synchronized between each sub-proxy server and between each sub-proxy server and the primary proxy server are different.

As an example, node 1 includes active Broker_a, standby Broker_b, and Broker_c, node 2 includes active Broker_b, standby Broker_a, and Broker_c, and node 3 includes active Broker_c, standby Broker_a, and Broker_b.

Among them, the copy group can refer to a group of Brokers with the same message, which can usually be composed of one master and N standby. Other sub-proxy servers synchronize messages, and when the main proxy server fails and goes down, the rest of the sub-proxy servers can provide read services.

In the embodiment of this application, the proxy servers included in each node do not belong to the same copy group, that is, the messages synchronized between the sub-proxy servers located under the same node and between the sub-proxy servers and the primary proxy server different, each node has a copy in each copy group when each copy group (for example, one primary Broker_a, two standby Broker_a, one primary Broker_b, two standby Broker_b, and one primary Broker_c, two standby Broker_c) works normally, Indicates that any node has the full amount of messages of the message broker service cluster. Under this framework, as long as one of the nodes (such as node 1, node 2 or node 3) of the message broker service cluster is in a normal working state, no Message lost.

In addition, each node includes a master proxy server Master Broker, which can provide read and write services to ensure that the capabilities of each node are equal.

In practical applications, this architecture can be applied to the core base of the second-level RTO (Recovery Time Objective) architecture of message middleware. Among them, RTO reflects the timeliness index of data center service recovery, which can be used to indicate the time required for service from interruption to recovery. The smaller the RTO value, the stronger the data recovery capability of the disaster recovery system.

It should be noted that the nodes in the message broker service cluster can refer to an environment with independent resources such as computing, memory, storage, and network, which can be physical machines, virtual machines, or containers, and realize the communication between producers and consumers. message transmission; and all Brokers in the same node are in the same process, that is, the Broker Container process, which is responsible for managing the Broker and serving as a shared network layer for all Brokers (all RPCs (Remote Procedure Call, Remote Procedure Call, It is a remote procedure call, and the HTTP request itself can also be regarded as a specific form of RPC) All requests need to be processed through the network layer of the Broker Container.

Referring to FIG. 3 , it shows a flow chart of the steps of an embodiment of a message communication method of the present application, which is applied to a message system. The message system includes a producer, a message broker service cluster and a consumer, and the message broker service cluster includes multiple nodes. Specifically, the following steps may be included:

Step 301, after the main proxy server of a node receives the message sent by the producer, it synchronizes the message with the secondary proxy server of at least one other node;

In the embodiment of this application, the message broker service cluster can realize the message transmission between the producer and the consumer. Specifically, the nodes included in the message broker service cluster can receive the message sent by the producer and respond to the message sent by the consumer. The message consumption request is implemented by sending a message to the consumer.

In the process of realizing message transmission between producers and consumers, it is first necessary to synchronize messages to realize message transmission in a distributed message system, avoid message transmission failures caused by failures, and provide failover for message systems ability.

In one embodiment of the present application, in the process of message synchronization, it is necessary to synchronize messages to other secondary proxy servers in the same copy group through the primary proxy server, and each node of the message proxy service cluster includes a primary proxy The server and at least one secondary proxy server do not belong to the same copy group, that is, the messages synchronized between the secondary proxy servers under the same node, and between the secondary proxy server and the primary proxy server are different. At this time, in the message proxy service node After receiving the message sent by the producer, the primary proxy server can synchronize the message with the sub-proxy server of at least one other node to ensure that each node contains a copy of each copy group, so that each node has this message The agent serves the full amount of messages of the cluster to ensure the message consistency of each node.

As an example, for a message broker service cluster with 3 masters and 6 backups, the master Broker_a of node 1 can perform message synchronization with the slave Broker_a of node 2 and the slave Broker_a of node 3, and the master Broker_b of node 2 can synchronize with the node The standby Broker_b in node 1 and the standby Broker_b in node 3 perform message synchronization, and the active Broker_c of node 3 can perform message synchronization with the standby Broker_c in node 1 and the standby Broker_c in node 3.

In step 302, the main proxy server sends a message to the consumer, or the secondary server of another node sends a message to the consumer.

After the message is synchronized by each node of the message broker service cluster, the message can be sent to the consumer through the nodes of the message broker service cluster, so as to realize the message transmission between the producer and the consumer.

Specifically, each node in the message proxy service cluster may include a primary proxy server and at least one sub-proxy server. During the process of sending a message, based on the working status of the node, the primary proxy server of a certain node may send messages to the consumer The sender sends a message, or the secondary server of another node sends a message to the consumer.

In one case, when the working status of a certain node is in the normal working state, the message can be sent directly to the consumer through the main proxy server of a certain node; In the machine state, the secondary server of another node can be used to send messages to consumers, and the secondary server of another node and the primary proxy server of a certain node belong to the same copy group, so that the process of message transmission without primary selection can be realized.

In the embodiment of this application, a message processing method applied to a message system is proposed, mainly through the nodes of the message broker service cluster to realize message transmission with producers and consumers, wherein each node in the message broker service cluster can It includes a copy of each copy group, and includes a primary proxy server and at least one secondary proxy server belonging to different copy groups. After the primary proxy server of a node receives the message sent by the producer, it can communicate with at least one other node. The secondary proxy server performs message synchronization, and its primary proxy server or another node's secondary proxy server can send messages to consumers. By proposing a new message queue high-availability architecture in which each node includes a master proxy server belonging to a different copy group and at least one sub-proxy server, it can realize single-point multi-Broker, improve the utilization rate of nodes in the message proxy service cluster, and reduce the resource consumption of nodes. waste; and because each node includes a master proxy server, it can ensure that the capabilities of each node are equal, and through the message synchronization of the master and sub-proxy servers between different nodes, under the premise of ensuring the consistency of each node's messages, It can realize node message transmission, especially the non-election process in the case of node failure.

Referring to FIG. 4 , it shows a flow chart of the steps of another embodiment of the message communication method of the present application, which is mainly the case where each node in the message broker service cluster is in a normal working state to process the message. Specifically, it can be Including the following steps:

Step 401, after the primary proxy server of a node receives the message sent by the producer, it synchronizes the message with at least one secondary proxy server belonging to the same copy group as the primary proxy server;

In the embodiment of this application, each node of the message proxy service cluster includes a primary proxy server and at least one secondary proxy server that do not belong to the same copy group, that is, between the secondary proxy servers under the same node, and the secondary proxy server The messages synchronized between the server and the main proxy server are different. In the process of message synchronization, the main proxy server in the message proxy service node can communicate with the secondary proxy server of at least one other node after receiving the message sent by the producer. Message synchronization is carried out so that each node has the full amount of messages of the message broker service cluster to ensure the message consistency of each node.

Wherein, the message consistency may refer to that the message consistency of each copy in the copy group can be achieved through an agreed mechanism in the copy group. Specifically, in the process of message synchronization between the primary proxy server of a node and the secondary proxy server of at least one other node, message synchronization can be performed with at least one secondary proxy server that the primary proxy server belongs to the same replica group, wherein, the primary proxy server belonging to the same replica group Each sub-proxy server and the primary proxy server of the group (that is, the same copy group) are located on different nodes.

In this embodiment of the application, message synchronization between agents belonging to the same copy group may refer to data synchronization, and the data may include Commit Log, topic, subscription relationship, metadata, etc. Referring to FIG. 5 , it shows a schematic diagram of the process of data synchronization in the embodiment of the present application. The message synchronization of each replica group can be realized through the data synchronization flow between each node. As an example, when the master proxy server Master Broker of Broker_a is performing real-time data synchronization to the secondary proxy server Slave Broker, it can be synchronized to the standby Broker_a located in nodes 2 and 3 through the data synchronization flow from the master Broker_a located in node 1 data.

Among them, in most cases, the replica group relies on this link to achieve message consistency within the replica group.

In a preferred embodiment, the copy group can also support changing the configuration to determine the consistency guarantee strength to support the dynamic downgrade strategy, which can trade off between availability and consistency, and realize the message consistency strength Configuration, which can be implemented based on the number of proxy servers configured to synchronize messages.

Specifically, you can configure the number of proxy servers for message synchronization with the primary proxy server, and then synchronize the messages sent by the producer to the proxy servers belonging to the same replica group according to the configured proxy server number, and realize the message synchronization based on the configured proxy server number. Strong consistency and/or weak consistency synchronization. Among them, the consistency configuration can refer to when the producer sends a message to a master proxy server, how many Brokers need to ensure that the message is sent successfully, that is, the strong consistency configuration and the weak consistency configuration can be It is the condition when the message received by the producer sends a successful response.

Configure message consistency strength. In the first case, when the configuration is strong consistency configuration, it means that each copy group in the message broker service cluster does not allow message inconsistency, that is, the producer is in the When sending a message to a master proxy server, the master proxy server needs to synchronize the message with all the sub-proxy servers in its copy group, and only after ensuring that the message is synchronized to all the sub-proxy servers in the copy group will it send the message to the producer The sender returns a successful response, indicating that the message has been sent successfully; if some sub-proxy servers in the copy group of the primary proxy server fail to synchronize the message or there is no sub-proxy server that successfully synchronizes the message, it means that the message has failed to be sent. The sender will automatically retry sending until the sender receives a successful response or the sender reaches the threshold of retry sending times.

However, in this strong consistency configuration mode, any message will be saved on all message proxy servers in the replica group at the same time, which can achieve strong message consistency, but when any proxy server fails, the sending Unavailable phenomena, such as when a node jitters and synchronization fails, the sending request will directly fail, reducing availability.

As an example, for a message broker service cluster with 3 masters and 6 backups, each copy group includes 1 master and 2 backups. Assume that the current configuration requires 3 proxy servers to synchronize messages, that is, 1 master and 2 slaves in the copy group Both need to perform message synchronization. Currently, in the case of strong consistency configuration, for example, each message sent to Broker_a Master in Node 1 needs to wait for the message to be synchronized to the two Slave brokers in Node 2 and Node 3. The message is considered to have been sent successfully.

In the second case, when configured as a weak consistency configuration, it means that each copy group in the message broker service cluster allows message inconsistency, that is, when the producer sends a message to a master proxy server , the primary proxy server can synchronize messages to some of the sub-proxy servers in its copy group, and after ensuring that the message is synchronized to some of the configured sub-proxy servers, it can return a successful response to the sender in the producer, indicating that this Message sent successfully.

In this case, each message sent to Broker_a Master can only be synchronized to one sub-proxy server, or even zero sub-proxy servers can be considered as successfully sent. However, in this weak consistency configuration mode, If a node goes down, it may cause message loss, and the strong consistency of messages in the replica group cannot be guaranteed. However, in this mode of weak consistency configuration, even if some nodes jitter and cause synchronization failure, it can be considered Sent successfully with higher availability.

It should be noted that the use of weak consistency configuration does not mean that only some sub-proxy servers will receive message synchronization, but that the main proxy server only needs to wait for some sub-proxy servers before returning a successful response to the sender. Synchronization is successful. At this time, the message synchronization of other sub-proxy servers remaining in its copy group is still in progress asynchronously.

As an example, for a message proxy service cluster with 3 masters and 6 backups, each copy group includes 1 master and 2 backups. Assume that the current configuration requires 3 proxy servers that need to synchronize messages. Assume that the current configuration requires proxy servers that need to synchronize messages The number is 1, that is, one master in the replica group needs to perform message synchronization. As long as the Master receives the message, it can immediately return a successful response without waiting for the message synchronization to complete. This configuration has high availability (even if the two Slaves are both A failure does not affect message sending), but the consistency of the message is low (the sender receives a successful response only to ensure that the Master has received the message, but cannot confirm that the message has been synchronized to other Slaves, or in other words, assuming that synchronization has occurred Failure, it may cause a message to exist only in the Master, but not in a Slave, that is, message inconsistency occurs).

It should be noted that the above configuration can be changed at any time and takes effect in real time, and does not limit the timing of consistent configuration, and the configuration can be adjusted after weighing availability and consistency according to actual service scenarios.

In an optional embodiment, the configuration of strong consistency of messages can ensure the strong consistency of messages in the replica group, but the availability is weak, while the configuration of weak consistency of messages cannot guarantee the strong consistency of messages in the replica group. However, its availability is very high. In addition to the configuration of the message strong consistency mode and message weak consistency mode mentioned above, the automatic downgrade mode can also be configured at this time to further support the dynamic downgrade strategy and flexibly balance availability and reliability.

The configured auto-degradation mode can mean that the master proxy server can calculate how many Brokers a message needs to be synchronized to before it is considered successful according to the synchronization status of the current replica group and a configurable synchronization number threshold.

In practical applications, when the synchronization status of the copy group is good, the strong consistency synchronization mode is used, that is, the message needs to be synchronized to all slaves before it is considered to be sent successfully. However, when the synchronization fails due to jitter or downtime in the copy group, the automatic Downgrade to weak consistency mode, so that the message can be considered as successfully sent when it is synchronized to some Slaves, that is, enabling the automatic downgrade strategy can accept that when some Brokers experience jitter, sacrifice consistency in exchange for availability, and the synchronization number threshold is used for The lower limit of acceptable consistency loss is specified, which can ensure availability on the basis of strong message consistency.

It should be noted that the automatic downgrade configuration is also changed at any time and takes effect in real time, and the timing of the automatic downgrade configuration is not limited.

As an example, for a message broker service cluster with 3 masters and 6 backups, each copy group includes 1 master and 2 backups. Assume that the current configured mode is a strong consistency configuration, that is, 1 master and 2 slaves in the copy group If message synchronization is required, after the automatic downgrade mode is enabled, assuming that the synchronization number threshold is set to 2, then according to the synchronization status of the current replica group, the calculated final number of Brokers to be synchronized can be 3 (both Slaves and Master are in Real-time synchronization status), can also be 2 (when a Slave synchronization progress lags behind the Master too much), but cannot be 1 (when it is 1, generally both Slave synchronization progress lags behind the Master too much, but because the synchronization number is configured The threshold is 2, so in this case, sending a message will directly return failure).

Step 402, send a message to the consumer through the main proxy server.

After the message is synchronized by each node of the message broker service cluster, a message can be sent to the consumer based on the working status of the node. When each node in the message broker service cluster is in a normal working Send a message to the consumer to complete the message transmission between the producer and the consumer.

Specifically, as shown in Figure 6, when each node in the message broker service cluster is in a normal working state, the node can receive the message sent by the producer and respond to the message consumption request sent by the consumer. The master proxy server sends messages to consumers, that is, the producer only sends messages to the Master of each replica group, and the consumer only consumes messages from the Master of each replica group.

In practical applications, different Brokers in the same node can be distinguished by different port numbers, that is, different brokers in the same node can listen to different port numbers, and by combining the node IP and port number, it is possible to determine which Broker to send the request to , specifically, you can specify the address IP:Port when sending the request to decide which broker to send the request to.

In a specific implementation, the message consumption request received by the message broker service cluster may include the node communication address and the proxy service port number. At this time, the target node can be determined according to the node communication address, and then the target node can be determined from the target node according to the proxy service port number. Proxy server, so that the target proxy server sends the target message to the consumer.

In the embodiment of this application, by proposing a new message queue high-availability architecture in which each node includes a primary proxy server and at least one secondary proxy server, single-point multi-Broker is realized, the utilization rate of nodes in the message proxy service cluster is improved, and the number of nodes is reduced. waste of resources; and since each node includes a primary proxy server belonging to a different copy group, it can ensure that the capabilities of each node are equal, and through the message synchronization of the primary and secondary proxy servers between different nodes, it is guaranteed that each node Under the premise of message consistency, it is possible to realize the no-election process of node message transmission, especially in the case of node failure.

Referring to FIG. 7 , it shows a flow chart of the steps of another message communication method embodiment of the present application, which is mainly for processing messages when a certain node in the message broker service cluster fails and goes down, and may specifically include Follow the steps below:

Step 701, after the primary proxy server of a node receives the message sent by the producer, it synchronizes the message with at least one secondary proxy server belonging to the same copy group as the primary proxy server;

In practical applications, message consistency configuration for message synchronization can be implemented based on the number of proxy servers configured to synchronize messages, including strong consistency configuration, weak consistency configuration, and automatic downgrade mode. Specifically, availability and consistency can be adjusted according to actual service scenarios. Adjust this configuration after making trade-offs. It should be noted that the configuration can be changed at any time and takes effect in real time, and the timing of configuration is not limited.

Step 702, the secondary proxy server of another node sends a message to the consumer when the primary proxy server fails.

After the message is synchronized by each node of the message broker service cluster, a message can be sent to the consumer based on the working status of the node. When the main proxy server of a node in the message broker service cluster is down, A message can be sent to the consumer through the sub-proxy server of another node to complete the message transmission between the producer and the consumer.

Specifically, the secondary proxy server that sends messages to the consumer may be a secondary proxy server that belongs to the same copy group as the primary proxy server.

Specifically, as shown in Figure 8, assuming that Node 1 is down, Producer stops sending messages to Broker_a Master, and at this time Consumer automatically switches the consumption request originally sent to Broker_a Master to Broker_a Slave on Node 2, because Broker_a Slave owns Broker_a Master The full amount of messages, so in the case of node 1 downtime, the availability of the service is still guaranteed, and the process does not need to be elected.

In a preferred embodiment, after a faulty node is repaired, the primary proxy server of the node can also be reverse-synchronized, that is, the secondary proxy server belonging to the same replica group on another node It can have the function of reverse synchronization of metadata, that is, reverse synchronization of metadata, where the synchronized metadata can refer to various stateful data used to record consumption and sending status of messages in the server, such as consumption location, consumption progress, timing message playback location, etc., to ensure the message consistency of each node.

Wherein, the message consistency may refer to that the message consistency of each copy in the copy group can be achieved through an agreed mechanism in the copy group. Specifically, the sub-proxy server of another node may perform reverse synchronization of metadata with the primary proxy server after the failure of the primary proxy server is repaired.

Referring to FIG. 9 , it shows a schematic diagram of the metadata reverse synchronization process in the embodiment of the present application. The metadata direction synchronization of each copy group is also realized through the metadata reverse synchronization flow between each node. The metadata reverse synchronization chain The road generally occurs when a node goes down and comes back online for data synchronization. As an example, assuming node 1 fails and goes down, the consumer can switch to Broker_a Slave in node 2 for consumption. At this time, the metadata generated by consumption, such as consumption progress, etc., can be reversely synchronized to Broker_a in node 1 Master, so that when the consumption traffic is switched back to Broker_a Master, it can be consumed according to the current consumption progress, that is, when consumers consume Broker_a Master in the re-online node 1, it can prevent the re-online Broker_a Master from following the original failure Consume according to the recorded consumption progress to avoid repeated consumption.

In the specific implementation, in the architecture of the new message queue middleware, there is no link for the slave broker server to directly send messages to the master broker server. The reverse metadata synchronization link implemented in the architecture can be As shown in Figure 9.

Among them, metadata reverse synchronization can be achieved by packaging metadata into messages.

Assuming that Node 1 fails and goes down, the consumer can switch to Broker_a Slave in Node 2 for consumption. At this time, Broker_a Slave in Node 2 performs metadata reverse synchronization process for Broker_a Master in Node 1 after the fault recovery can be as follows:

(1) First, Broker_a Slave in node 2 can package metadata into a message and write it to Broker_b Master; (2) Then Broker_b Master in node 2 can synchronize the message to node 1 through the message synchronization link in a above and the Broker_b Slave of node 3; (3) Broker_a Master in node 1 and Broker_a Slave in node 3 can respectively read the message from the Broker_b Slave of their respective nodes and parse out the metadata to be synchronized, update it locally, and complete Reverse synchronization of metadata.

In practical applications, the reverse synchronization of metadata can be done by packaging the metadata into a message and writing it to the Broker_b Master of the same node. The way to determine the metadata that needs to be synchronized can be realized through the Topic of the message.

Specifically, the metadata that requires reverse synchronization, that is, the message packaged into the metadata can have a special Topic, and the message can be synchronized to the Broker_b Slave of node 1 and the Broker_b Slave of node 3 through the data synchronization link. And Broker_a Master and Broker_a Slave will monitor the number of messages of this special topic on other Brokers on the same node. When the number of messages changes, they can consume new messages and parse them into metadata, and then update them to their own messages to realize metadata reverse synchronization.

In the embodiment of this application, by proposing a new message queue high-availability architecture in which each node includes a primary proxy server and at least one secondary proxy server, single-point multi-Broker is realized, the utilization rate of nodes in the message proxy service cluster is improved, and the number of nodes is reduced. Waste of resources; and because each node includes a master proxy server, it can ensure that the capabilities of each node are equal, and through the message synchronization of the master and sub-proxy servers between different nodes, the premise of ensuring the consistency of each node's messages Under this condition, it is possible to realize the non-election master process when the node message is transmitted, especially when the node fails.

In this embodiment of the application, the message system may adopt a distributed system. In a distributed message system, there may be multiple servers that produce messages and consume messages. Multiple servers may form a server cluster, that is, producers may refer to production A consumer cluster may refer to a consumer cluster.

Referring to Fig. 10, it shows a schematic diagram of the framework of the message communication system in the embodiment of the present application, the message system may include a producer cluster 1001 (Producer cluster), a message broker service cluster 1002 (Broker cluster), a domain name server cluster 1003 (Name Server cluster) ) and consumer cluster 1004 (Consumer cluster), wherein each message broker service cluster may include a plurality of nodes, each node includes a copy of each copy group, and includes a master proxy server belonging to a different copy group and at least A proxy server.

In this messaging system, the Producer cluster 1001 can be used to produce and send messages, which mainly sends data to consumers through Topic; the Broker cluster 1002, as a proxy server in the messaging system, can provide external messages The sending interface and consumption interface, that is, as the intermediary between the Producer cluster and the Consumer cluster; the Name Server cluster 1003 is mainly used for the management of source data, including the management of Topic and routing information, which can be used to provide Topic-Broker Relational data, and each message proxy server Broker needs to register with the Name Server when it starts, and the Producer cluster 1001 can obtain the routing information of the corresponding message proxy server Broker from the Name Server 1003 according to the topic corresponding to the message before sending the message, and the Consumer cluster 1004 It is also possible to regularly obtain the routing information of the Topic, so as to realize the message forwarding of the message proxy server Broker through the relational data of the Topic-Broker; the Consumer cluster 1004 is used to obtain the messages produced by the Producer cluster, which can be realized by subscribing to the Topic.

Specifically, the message processing process of the message system can receive the message sent by the producer cluster through the node of the message proxy server Broker. The messages synchronized between each secondary proxy server and the primary proxy server in the same node are different, that is, each secondary proxy Different from the messages synchronized between the main proxy servers and each sub-proxy server, at this time the node can respond to the message consumption request sent by the consumer cluster, and send the target message to the consumer cluster through the target proxy server of the message proxy service node.

In practical applications, after the primary proxy server of a node receives the message sent by the producer cluster, it can synchronize the message with the secondary proxy server of at least one other node; the primary proxy server sends a message to the consumer cluster, or another node The secondary server sends messages to the consumer cluster.

It should be noted that, for the method embodiment, for the sake of simple description, it is expressed as a series of action combinations, but those skilled in the art should know that the embodiment of the present application is not limited by the described action sequence, because According to the embodiment of the present application, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification belong to preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present application.

Referring to FIG. 11 , it shows a structural block diagram of an embodiment of a message communication device of the present application. The message system includes a producer, a message broker service cluster, and a consumer. The message broker service cluster includes multiple nodes, and each node includes each A copy of the copy group, and includes a master proxy server and at least one secondary proxy server belonging to different copy groups, specifically may include the following modules:

The message synchronization module 1101 is located at the main proxy server of a node, and is used to perform message synchronization with the secondary proxy server of at least one other node after receiving the message sent by the producer;

The first message sending module 1102, located in the main proxy server, is used to send messages to consumers;

The second message sending module 1103 is located at the secondary server of another node, and is used to send messages to consumers.

In an embodiment of the present application, the message synchronization module 1101 may include the following submodules:

In an embodiment of the present application, the message synchronization submodule may include the following units:

In an embodiment of the present application, the device may also include the following modules:

In an embodiment of the present application, the metadata reverse synchronization module may include the following submodules:

In an embodiment of the present application, the second message sending module may include the following submodules:

As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment.

The embodiment of the present application also provides an electronic device, including: a processor, a memory, and a computer program stored on the memory and capable of running on the processor. When the computer program is executed by the processor, the above message communication method embodiment is implemented. Each process can achieve the same technical effect, so in order to avoid repetition, it will not be repeated here.

The embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, each process of the above message communication method embodiment is realized, and the same technical effect can be achieved , to avoid repetition, it will not be repeated here.

Each embodiment in the description is described in a progressive manner, and each embodiment focuses on the difference from other embodiments, and the same and similar parts of each embodiment can be referred to each other.

Those skilled in the art should understand that the embodiments of the embodiments of the present application may be provided as methods, devices, or computer program products. Therefore, the embodiment of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

Embodiments of the present application are described with reference to flowcharts and/or block diagrams of methods, terminal devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor or processor of other programmable message processing terminal equipment to produce a machine such that the instructions executed by the computer or other programmable message processing terminal equipment processor Produce means for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable message processing terminal to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the The instruction means implements the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded into a computer or other programmable message processing terminal equipment, so that a series of operational steps are performed on the computer or other programmable terminal equipment to produce computer-implemented processing, thereby The instructions executed above provide steps for implementing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

While the preferred embodiments of the embodiments of the present application have been described, additional changes and modifications can be made to these embodiments by those skilled in the art once the basic inventive concept is understood. Therefore, the appended claims are intended to be interpreted to cover the preferred embodiment and all changes and modifications that fall within the scope of the embodiments of the application.

Finally, it should also be noted that in this text, relational terms such as first and second etc. are only used to distinguish one entity or operation from another, and do not necessarily require or imply that these entities or operations, any such actual relationship or order exists. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or terminal equipment comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements identified, or also include elements inherent in such a process, method, article, or end-equipment. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article or terminal equipment comprising the element.

A message communication method and a message communication device provided by the application have been introduced in detail above. In this paper, specific examples are used to illustrate the principle and implementation of the application. The description of the above embodiments is only for helping Understand the method of this application and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of this application, there will be changes in the specific implementation and scope of application. In summary, the content of this specification should not be understood For the limitation of this application.

Claims

A message communication method, characterized in that it is applied to a message system, the message system includes a producer, a message broker service cluster, and a consumer, the message broker service cluster includes a plurality of nodes, and each node includes each copy group A replica of a replica, and includes a primary proxy server and at least one secondary proxy server belonging to different replica groups, the method comprising:

After the main proxy server of a node receives the message sent by the producer, it synchronizes the message with the secondary proxy server of at least one other node;

The primary proxy server sends messages to consumers, or the secondary server of another node sends messages to consumers.
The method according to claim 1, wherein the message synchronization with the secondary proxy server of at least one other node comprises:

Perform message synchronization with at least one secondary proxy server belonging to the same copy group as the primary proxy server; wherein, the secondary proxy servers belonging to the same copy group and the primary proxy server are located at different nodes.
The method according to claim 2, wherein synchronizing the message sent by the producer to at least one secondary proxy server belonging to the same copy group as the primary proxy server comprises:

Configure the number of proxy servers for message synchronization with the master proxy server;

According to the configured number of proxy servers, the messages sent by the producer are synchronized with the proxy servers belonging to the same replica group.
The method according to claim 1, further comprising:

The secondary proxy server of another node synchronizes the current metadata with the primary proxy server.
The method according to claim 4, wherein the secondary proxy server of the other node synchronizes the current metadata with the primary proxy server, comprising:

A secondary proxy server belonging to the same copy group as the primary proxy server synchronizes current metadata with the primary proxy server after the fault of the primary proxy server is repaired.
The method according to claim 1, wherein the secondary server of the other node sends a message to the consumer, including:

The secondary proxy server of another node sends a message to the consumer when the primary proxy server fails.
The method according to claim 6, wherein the sub-proxy server of the other node sends a message to the consumer, including:

Messages are sent to the consumer through a secondary proxy server belonging to the same replica group as the primary proxy server.
A message communication device, characterized in that it is applied to a message system, the message system includes a producer, a message broker service cluster, and a consumer, the message broker service cluster includes a plurality of nodes, and each node includes each copy group A replica of the device, and includes a master proxy server and at least one secondary proxy server belonging to different replica groups, the device includes:

The message synchronization module is located at the main proxy server of one node, and is used to perform message synchronization with the secondary proxy server of at least one other node after receiving the message sent by the producer;

The first message sending module is located in the main proxy server and is used to send messages to consumers;

The second message sending module is located in the secondary server of another node, and is used to send messages to consumers.
An electronic device, characterized by comprising: a processor, a memory, and a computer program stored on the memory and capable of running on the processor, when the computer program is executed by the processor, it realizes the claims Steps of the message communication method described in any one of 1-7.
A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the message communication method according to any one of claims 1 to 7 is implemented. step.
A computer program, characterized in that, when the computer program is executed by a processor, the electronic device executes the steps of the message communication method according to any one of claims 1-7.