WO2022033586A1 - Message sending method and device - Google Patents

Abstract

Provided by the present application are a message sending and device. In the present application, a current service message is read from a local disk, and the current service message is sent to a message queue cluster. If the current service message fails to be sent, a new service message will be generated according to the current service message, and the new service message is added to and stored in the local disk so as to await sending again. By means of the embodiments of the present application, on the one hand, the service message that fails to be sent may be sent again, thus avoiding the loss of the service message; and on the other hand, the service message that fails to be sent is stored on a local disk, so that a disaster recovery solution does not depend on other servers.

Description

A message sending method and device technical field

The embodiments of the present application relate to the field of data transmission, and in particular, to a method and apparatus for sending a message.

Background technique

Queue is a first-in, first-out data structure. Distributed message queues can be regarded as deploying this data structure to an independent server. Applications can use distributed message queues through remote access interfaces to perform message access operations, and then Implement distributed asynchronous calls. If the sender does not have disaster recovery means when the message sending fails, then when the distributed message queue fails, the message to be sent will be lost, which will make the application function unavailable. In the related art, the disaster recovery method in the face of message sending failure is usually to make a compensation at the application layer of the sender, but this will increase the workload of the sender to access the distributed message queue.

SUMMARY OF THE INVENTION

The following is an overview of the topics detailed in this article. This summary is not intended to limit the scope of protection of the claims.

The embodiments of the present application provide a message sending method and device, which can overcome the problem in the related art that the disaster recovery method when the message sending fails will increase the workload of the sender accessing the distributed message queue.

A first aspect of an embodiment of the present application provides a message sending method, including: reading a current service message from a local disk, where the current service message is a service message to be sent pointed to by a reference identifier stored in the local disk; sending a message to a message queue cluster For the current service message, update the reference ID so that the reference ID points to the next service message to be sent after the current service message in the local disk; for the case where the current service message fails to be sent, a new service message is generated according to the current service message, and the After the new service message is stored in the local disk of all service messages to be sent, the content of the current service message is the same as that of the new service message.

In an exemplary instance, for the situation that the current service message is successfully sent, the method further includes: returning the step of reading the current service message from the local disk;

After storing the new service message in the local disk, the method further includes: returning to the step of reading the current service message from the local disk.

In an exemplary example, before the step of returning to the step of reading the current service message from the local disk, the method further includes: judging whether the current sending task is terminated; for the case that the current sending task is not terminated, continuing to execute the Return to the step of reading the current service message from the local disk as described above; in the case of termination of the current sending task, stop sending the service message.

In an exemplary example, before reading the current service message from the local disk, the method further includes: scanning the local disk for service messages to be sent; judging that there are service messages to be sent in the local disk, and judging the message queue cluster Is it normal? It is judged that the message queue cluster is normal, and continues to perform the steps of reading the current business message from the local disk.

In an exemplary example, the service message is set with a corresponding number, and the number is used to reflect the sending order of the service message; the scanning of the local disk for whether there is a service message to be sent includes: judging whether there is a number in the local disk The service message whose number is greater than the service message to be sent pointed to by the reference identifier is determined as the service message to be sent.

In an exemplary example, the service message to be sent includes a first identifier, and the first identifier is used to indicate that the service message has not been sent; the scanning whether there is a service message to be sent in the local disk includes: judging whether there is a service message in the local disk Whether there is a service message containing the first identifier; determining the service message containing the first identifier as a service message to be sent.

In an exemplary example, determining whether the message queue cluster is normal includes: querying whether the address of the message queue cluster exists in the routing table; determining that the message queue cluster is normal if the address of the message queue cluster exists in the routing table.

In a second aspect of the embodiments of the present application, you provide a message sending device, including: an obtaining module, configured to read a current service message from a local disk, where the current service message is a service to be sent pointed to by a reference identifier stored in the local disk message; the sending module is used to send the current business message to the message queue cluster, and update the benchmark identifier so that the benchmark identifier points to the next business message to be sent after the current business message in the local disk; the processing module, if the current business message fails to be sent , the business message additional storage module is used to generate a new business message according to the current business message, and store the new business message in the local disk after all to-be-sent business messages, the content of the current business message and the new business message are the same.

A third aspect of the embodiments of the present application provides a computer device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by at least one processor. A processor executes, thereby executing the message sending method provided by the first aspect of the embodiments of the present application.

A fourth aspect of the embodiments of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores computer instructions, and the computer instructions are used to cause a computer to execute the message sending method provided by the first aspect of the embodiments of the present application.

The technical solution of the present application has the following advantages:

The message sending method and device provided by the embodiments of the present application read from the local disk and send the current business message pointed to by the reference identifier to the message queue cluster, and if the sending fails, assemble the current business message into a new business message and additionally store it. After all pending business messages on the local disk. The embodiment of the present application provides a disaster recovery solution when the service message fails to be sent. When the service message fails to be sent, the service message that fails to be sent is stored in the local disk. On the one hand, the service message that fails to be sent can be restored Sending, avoiding the loss of business messages, on the other hand, storing business messages that fail to be sent on the local disk, so that the disaster recovery solution does not depend on other servers.

Additional features and advantages of embodiments of the present application will be set forth in the description that follows, and in part will be apparent from the description, or may be learned by practice of the present application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the description, claims and drawings.

Other aspects will become apparent upon reading and understanding of the drawings and detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings described herein are used to provide further understanding of the present application and constitute a part of the present application. The schematic embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation of the present application. In the attached image:

FIG. 1 is a flowchart of an example of a message sending method in an embodiment of the present application;

FIG. 2 is a flowchart of another example of a message sending method in an embodiment of the present application;

3 is a flowchart of another example of a message sending method in an embodiment of the present application;

4 is a schematic block diagram of an example of a message sending apparatus in an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a computer device provided in an embodiment of the present application.

detail

Hereinafter, the present application will be described in detail with reference to the accompanying drawings and in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features of the embodiments may be combined with each other in the case of no conflict.

The technical solutions of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

In the description of this application, it should be noted that the terms "first" and "second" are only used for description purposes, and cannot be understood as indicating or implying relative importance.

In addition, the technical features involved in the different embodiments of the present application described below can be combined with each other as long as there is no conflict with each other.

Example 1

Queue is a first-in, first-out data structure. Distributed message queues can be regarded as deploying this data structure to an independent server. Applications can use distributed message queues through remote access interfaces to perform message access operations, and then Implement distributed asynchronous calls. When the distributed message queue fails, it will cause the message to be sent to be lost, thereby making the application function unavailable.

An embodiment of the present application provides a method for sending a message, which is applied to a sender, as shown in FIG. 1 , including:

Step S10: read the current service message from the local disk, and the current service message is the service message to be sent pointed to by the reference identifier stored in the local disk;

Step S20: Send the current service message to the message queue cluster, and update the reference identifier so that the reference identifier points to the next service message to be sent after the current service message in the local disk.

In an exemplary instance, there are multiple service messages stored in the sender's local disk, including sent service messages and to-be-sent service messages, and the reference identifier is updated every time a service message is sent, so that the reference identifier points to the next A to-be-sent service message can conveniently locate the next service message to be sent when the service message is sent, thereby avoiding retransmission or omission of the service message.

Step S30: Determine whether the current service message fails to be sent, if the sending fails, execute step S40, and if the sending is successful, return to the above-mentioned step S10.

In an exemplary instance, if the sender fails to send a business message to the message queue cluster, the message queue cluster will send feedback information indicating the failure to send the business message to the sender. In this way, the sender receives a message indicating that the business message is sent. The failure feedback information can be used to determine that the service message fails to be sent.

Step S40: Generate a new service message according to the current service message, and store the new service message in the local disk after all to-be-sent service messages, the content of the current service message and the new service message are the same, and return to step S10.

In an exemplary instance, the sent service message and the service message to be sent in the local disk can be distinguished in a certain way, and assembling the service message that fails to be sent into a new service message means that according to the current local disk The rule that distinguishes whether a business message has been sent in the rules assembles business messages that fail to be sent into business messages that are not sent.

The purpose of additionally storing the service message that fails to be sent in the local disk after all the service messages to be sent is to ensure that the service message that fails to be sent can be sent again without affecting the normal sending of other service messages. In an embodiment, an independent space may also be set aside in the local disk for storing service messages that fail to be sent. The message is sent again.

The message sending method provided by the embodiment of the present application reads from the local disk and sends the current service message pointed to by the reference identifier to the message queue cluster. If the sending fails, the current service message is assembled into a new service message and additionally stored locally. After all pending business messages on disk. The embodiment of the present application provides a disaster recovery solution when the service message fails to be sent. When the service message fails to be sent, the service message that fails to be sent is stored in the local disk. On the one hand, the service message that fails to be sent can be restored Sending, avoiding the loss of business messages, on the other hand, storing business messages that fail to be sent on the local disk, so that the disaster recovery solution does not depend on other servers.

In an exemplary example, as shown in FIG. 2 , in the message sending method provided by the embodiment of the present invention, before returning to step S10, the method further includes:

Step S50: Determine whether the current sending task is terminated. In one embodiment, in order to ensure the rational utilization of resources, the sender completes the sending of service messages at regular intervals, performs a sending task at regular intervals, and the time for each sending task is fixed. If the current sending task is not terminated, return to step S10, if the current sending task is terminated, stop sending the service message, and end the process.

In an exemplary example, as shown in FIG. 3 , before performing the foregoing step S10, the message sending method provided by this embodiment of the present application further includes:

Step S70: Scan the local disk for service messages to be sent. The messages to be sent by the sender are service messages to be sent. Therefore, when restarting the sending task, it is necessary to scan the local disk for service messages to be sent. If there is a service message to be sent in the local disk, step S80 is performed, and if there is no service message to be sent in the local disk, the current sending task is ended.

Step S80: Determine whether the message queue cluster is normal. Only when the message queue cluster is normal can the service message be sent successfully. Therefore, in order to avoid waste of resources, after restarting the sending task, it is necessary to first determine whether the message queue cluster is normal. If the queue cluster is normal, step S10 is performed. If the message queue cluster is abnormal, the current sending task is ended.

In an exemplary example, step S70 and step S80 may alternatively exist, that is, only the judgment of step S70 is performed before step S10 is performed, or only the judgment of step S80 is performed.

It should be noted that the detection of the message queue cluster can be detected only once at the beginning of the sending task, or it can be detected periodically during the execution of the sending task, or it can be detected every time before the service message to be sent is sent, but in order to complete the detection. For fast sending of the service to be sent, the embodiment of the present application only detects once at the beginning of the sending task, and in practical application, different detection rules can be selected according to actual requirements.

In an exemplary example, the service message is set with a corresponding number, and the number is used to reflect the sending order of the service message. The above step S70 may include:

Determine whether there is a service message with a number greater than the service message to be sent pointed to by the reference identifier in the local disk, and if so, determine the service message with a number greater than the service message to be sent pointed to by the reference identifier as a service message to be sent. In one embodiment, the sender extracts and sends the service messages in the order of the service message numbers. Then, the service messages whose numbers are smaller than the service messages to be sent pointed to by the reference identifier are the service messages that have been sent, and the service messages whose numbers are greater than the reference identifier are all sent. The service messages that point to the service message to be sent are all unsent service messages.

In an exemplary example, if each service message is set with a corresponding number, and the number is the order in which the service messages are sent, then in step S30, reassembling the service messages that fail to be sent means that the service message fails to be sent. A new number is distributed to the service message, which is greater than the number of all the service messages to be sent.

In an exemplary example, the service message to be sent includes a first identifier, and the first identifier is used to indicate that the service message has not been sent. The foregoing step S70 may include:

It is judged whether there is a service message containing the first identifier in the local disk, and if so, the service message containing the first identifier is judged as a service message to be sent.

In an embodiment, if the unsent service message is identified by the first identifier, in step S30, reassembling the service message that fails to send means adding the first identifier to the service message that fails to send , in this way, when sending the service message, the service message that fails to be sent may be determined as the service message to be sent to be sent again.

The above two ways of confirming the service message to be sent are only for illustration, and are not used to limit the protection scope of the present application.

In an exemplary example, the above step S80 may include:

Check whether the address of the message queue cluster exists in the routing table. If the address of the message queue cluster exists in the routing table, it is determined that the message queue cluster is normal. In one embodiment, if the IP address of a certain server exists in the routing table of the sender, it means that the sender can establish a connection with the server and complete the data transmission, but the IP address that does not exist in the routing table sends the The party cannot establish a connection with the server corresponding to the IP address. In one embodiment, when the message queue cluster is faulty, its IP address will not appear in the routing table of the sender, therefore, whether the message queue cluster is faulty can be detected by querying the routing table. It should be noted that only a simple detection of the message queue cluster can be performed through the routing table. Even if the address of the message queue cluster exists in the routing table, it cannot be guaranteed that the distributed message queue is normal, so even if there is a message queue in the routing table. The address of the cluster will still fail to send the message.

Example 2

An embodiment of the present application provides a message sending apparatus, as shown in FIG. 4 , including:

The obtaining module 10 is configured to read the current service message from the local disk, where the current service message is the service message to be sent pointed to by the reference identifier stored in the local disk. For a detailed description, see the description of step S10 in Embodiment 1 above.

The sending module 20 is used to send the current service message to the message queue cluster, and update the reference identifier, so that the reference identifier points to the next service message to be sent after the current service message in the local disk. For a detailed description, see the steps in the above-mentioned embodiment 1. Description of the S20.

The processing module 30 is used to generate a new business message according to the current business message in the case of failure to send the current business message, and store the new business message in the local disk after all the business messages to be sent, the current business message and the new business message. The content of the message is the same, and for a detailed description, see the description of step S30 and step S40 in Embodiment 1 above.

The message sending device provided by this application reads the current business message pointed to by the message queue cluster reference identifier from the local disk, and if the sending fails, assembles the current business message into a new business message and additionally stores all the pending business messages in the local disk. After sending a business message. The message sending device provided by the present application provides a disaster recovery solution when the service message fails to be sent. When the service message fails to be sent, the failed service message is stored in the local disk. On the one hand, the service message that fails to be sent can be stored. Sending again avoids the loss of business messages. On the other hand, business messages that fail to be sent are stored on the local disk, so that the disaster recovery solution does not depend on other servers.

Example 3

An embodiment of the present application provides a computer device. As shown in FIG. 5 , the computer device mainly includes one or more processors 61 and a memory 62 . In FIG. 5 , one processor 61 is used as an example.

The computer equipment may also include: an input device 63 and an output device 64 .

The processor 61 , the memory 62 , the input device 63 and the output device 64 may be connected by a bus or in other ways, and the connection by a bus is taken as an example in FIG. 5 .

The processor 61 may be a central processing unit (Central Processing Unit, CPU). The processor 61 can also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other Chips such as programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above types of chips. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The memory 62 may include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the messaging device, and the like. Additionally, memory 62 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, memory 62 may optionally include memory located remotely from processor 61 that may be connected to the messaging device via a network. The input device 63 may receive user input of computational requests (or other numerical or character information) and generate key signal input associated with the messaging device. The output device 64 may include a display device such as a display screen, and is used to output the calculation result.

Example 4

The embodiments of the present application provide a computer-readable storage medium, where the computer-readable storage medium stores computer instructions, and the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions can execute the message sending method in any of the foregoing method embodiments . The storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a flash memory (Flash Memory), a hard disk (Hard Disk Drive) , abbreviation: HDD) or solid-state drive (Solid-State Drive, SSD), etc.; the storage medium may also include a combination of the above-mentioned types of memories.

Obviously, the above-mentioned embodiments are only examples for clear description, and are not intended to limit the implementation manner. For those of ordinary skill in the art, changes or modifications in other different forms can also be made on the basis of the above description. There is no need and cannot be exhaustive of all implementations here. And the obvious changes or changes derived from this are still within the scope of protection created by the present application.

The above descriptions are only preferred embodiments of the present application, and are not intended to limit the present application. For those skilled in the art, the present application may have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included within the protection scope of this application.

Claims (10)

A message sending method, comprising: Read the current service message from the local disk, where the current service message is the service message to be sent pointed to by the reference identifier stored in the local disk; Sending the current service message to a message queue cluster, and updating the reference identifier, so that the reference identifier points to the next service message to be sent after the current service message in the local disk; In the case where the sending of the current service message fails, a new service message is generated according to the current service message, and the new service message is stored in the local disk after all the service messages to be sent. The content of the new service message is the same. The message sending method according to claim 1, wherein, For the situation that the current service message is successfully sent, the method further includes: returning to the step of reading the current service message from the local disk; After storing the new service message in the local disk, the method further includes: returning to the step of reading the current service message from the local disk. The message sending method according to claim 2, wherein before the step of returning to the step of reading the current service message from the local disk, the method further comprises: Determine whether the current sending task is terminated; For the situation that the current sending task is not terminated, continue to perform the step of returning the described reading of the current service message from the local disk; In the case that the current sending task is terminated, the sending of the service message is stopped. The message sending method according to claim 1, 2 or 3, wherein before the reading the current service message from the local disk, the method further comprises: Scan the local disk to see if there is a service message to be sent; Judging that the service message to be sent exists in the local disk, and judging whether the message queue cluster is normal; It is judged that the message queue cluster is normal, and the step of reading the current service message from the local disk is continued. The message sending method according to claim 4, wherein the service message is provided with a serial number corresponding to it, and the serial number is used to reflect the sending order of the service message; The scanning whether the service message to be sent exists in the local disk includes: Judging whether there is a service message with a number greater than the service message to be sent pointed to by the reference identifier in the local disk; A service message whose number is greater than the service message to be sent pointed to by the reference identifier is determined as the service message to be sent. The message sending method according to claim 4, wherein the service message to be sent includes a first identifier, and the first identifier is used to indicate that the service message has not been sent; The scanning whether the service message to be sent exists in the local disk includes: judging whether there is a service message containing the first identifier in the local disk; The service message containing the first identifier is determined as the service message to be sent. The message sending method according to claim 4, wherein the judging whether the message queue cluster is normal comprises: query whether the address of the message queue cluster exists in the routing table; The address of the message queue cluster exists in the routing table, and it is determined that the message queue cluster is normal. A message sending device, comprising: an acquisition module, configured to read a current service message from a local disk, where the current service message is a service message to be sent pointed to by a reference identifier stored in the local disk; A sending module, configured to send the current service message to a message queue cluster, and update the reference identifier, so that the reference identifier points to the next service message to be sent after the current service message in the local disk; A processing module, where the current service message fails to be sent, and the service message storage module is configured to generate a new service message according to the current service message, and additionally store the new service message in the local disk for all to-be-sent messages After the service message, the content of the current service message and the new service message is the same. A computer device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the Instructions are executed by the at least one processor to perform the message sending method of any of claims 1-7. A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions, and the computer instructions are used to cause the computer to execute the message sending according to any one of claims 1-7 method.

Images