Message pushing method and system based on multiple queues

Abstract

The invention discloses a message pushing method and system based on multiple queues, and the number of timeout delay information of the queues is dynamically sensed by monitoring the actual pushing processing time of messages in priority queues. The quantity of the timeout time delay information can represent the congestion condition of the priority queue, so that the consumer quantity of the priority queue is automatically adjusted based on the quantity of the timeout time delay information, the consumer quantity of the priority queue is related to the congestion condition of the priority queue, and under the condition that the congestion occurs in the priority queue, the consumer quantity of the priority queue can be automatically adjusted. According to the embodiment of the invention, more consumers can be called to push messages in the priority queue, and the consumers in the priority queue can be reduced to save resources of a server under the condition that the priority queue is idle, so that the number of the consumers can be dynamically adjusted according to the actual condition, and the user experience is improved. And the risk of server resource waste caused by processing the messages according to a fixed number of consumers is reduced, so that the server resources are more fully utilized.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a message push method and system based on multiple queues. Background Art

[0002] With the development of computer software technology and information technology, more and more companies use message push services to push various messages to corresponding users, such as consumer, advertising or information information. The acceptable delay for different types of messages is also different. For example, the shorter the delay for consumer account information, verification code and other information, the better, while the delay for advertising and information messages can be longer.

[0003] Currently, the message push service pushes various messages to a fixed number of consumers. However, as the number of users continues to increase, the message volume of the upstream system continues to increase, and the server resources required by the message push service are also increasing, making it difficult to fully utilize the server resources. Summary of the invention

[0004] The present application provides a message push method and system based on multiple queues, which can more fully utilize server resources by dynamically adjusting the number of consumers in the priority queue according to actual conditions. The technical solution is as follows.

[0005] In a first aspect, a message push method based on multiple queues is provided, the method comprising:

[0006] receiving a push request, wherein the push request indicates that a message is pushed to a client;

[0007] adding a request timestamp to the message, and adding the message to a target queue that matches the priority of the message among multiple priority queues based on the priority of the message, wherein the request timestamp indicates a time point when the push request is received;

[0008] Consume the message in the target queue through a consumer, and push the message to the client;

[0009] Recording the processing completion timestamp of the message, where the processing completion timestamp indicates the time point when the message push is completed;

[0010] Based on the request timestamp stored in the message and the message processing completion timestamp of the message, obtaining the actual push processing time of the message, the actual push processing time being the time difference between the request timestamp and the message processing completion timestamp;

[0011] If the actual push processing time of the message is greater than the processing time threshold corresponding to the target queue, record the timeout delay information of the target queue;

[0012] The number of consumers of the target queue is adjusted based on the amount of timeout delay information of the target queue recorded within a sliding time window of a predetermined length.

[0013] In some implementations, adjusting the number of consumers of the target queue based on the amount of timeout delay information of the target queue recorded within a sliding time window of a predetermined length includes:

[0014] If the number of timeout delay information of the target queue recorded within a sliding time window of a predetermined length is greater than the number of warnings that can occur for the target queue, increase the number of consumers of the target queue and schedule the newly added consumers to consume messages in the target queue.

[0015] In some implementations, adjusting the number of consumers of the target queue based on the amount of timeout delay information of the target queue recorded within a sliding time window of a predetermined length includes:

[0016] If the number of timeout delay information of the target queue recorded within a sliding time window of a predetermined length is greater than the number of warnings that can occur for the target queue, and the current number of consumers of the target queue is less than the first consumer number threshold, increase the number of consumers of the target queue and schedule the newly added consumers to consume messages in the target queue.

[0017] In some implementations, adjusting the number of consumers of the target queue based on the amount of timeout delay information of the target queue recorded within a sliding time window of a predetermined length includes:

[0018] If the duration for which the target queue does not generate timeout delay information is greater than or equal to the duration threshold, and the number of unconsumed messages in the target queue is less than or equal to the message number threshold, reduce the number of consumers of the target queue.

[0019] In some implementations, adjusting the number of consumers of the target queue based on the amount of timeout delay information of the target queue recorded within a sliding time window of a predetermined length includes:

[0020] If the duration of no timeout delay information in the target queue is greater than or equal to the duration threshold, and the number of unconsumed messages in the target queue is less than or equal to the message number threshold, and the current number of consumers of the target queue is greater than the second consumer number threshold, reduce the number of consumers in the target queue.

[0021] In some implementations, reducing the number of consumers in the target queue includes:

[0022] Close the consumer of the target queue, or schedule the consumer of the target queue to another target queue with a higher priority than the target queue.

[0023] In a second aspect, a message push system based on multiple queues is provided, the system comprising:

[0024] A message access service, for receiving a push request, the push request indicating a message to be pushed to a client; adding a request timestamp to the message, and adding the message to a target queue that matches the priority of the message among multiple priority queues based on the priority of the message, the request timestamp indicating a time point when the push request is received;

[0025] A message consumer service is used to consume the message in the target queue through a consumer and push the message to the client; record the processing completion timestamp of the message, the processing completion timestamp indicates the time point when the message push is completed; based on the request timestamp saved in the message and the message processing completion timestamp of the message, obtain the actual push processing time of the message, the actual push processing time is the time difference between the request timestamp and the message processing completion timestamp; if the actual push processing time of the message is greater than the processing time threshold corresponding to the target queue, record the timeout delay information of the target queue, and send the timeout delay information to the management configuration center;

[0026] The management configuration center is used to adjust the number of consumers of the target queue based on the amount of timeout delay information of the target queue recorded within a sliding time window of a predetermined length.

[0027] In some embodiments, the management configuration center is used to add consumers to the target queue and schedule the newly added consumers to consume messages in the target queue if the number of timeout delay information of the target queue recorded within a sliding time window of a predetermined length is greater than the number of times an early warning of the target queue can occur.

[0028] In some embodiments, the management configuration center is used to add consumers to the target queue and schedule the newly added consumers to consume messages in the target queue if the number of timeout delay information of the target queue recorded within a sliding time window of a predetermined length is greater than the number of warnings that can occur for the target queue, and the current number of consumers of the target queue is less than a first consumer number threshold.

[0029] In some embodiments, the management configuration center is used to reduce the consumers of the target queue if the duration for which the target queue does not generate timeout delay information is greater than or equal to a duration threshold, and the number of unconsumed messages in the target queue is less than or equal to a message number threshold.

[0030] In some embodiments, the management configuration center is used to reduce the consumers of the target queue if the duration of the target queue without timeout delay information is greater than or equal to a duration threshold, and the number of unconsumed messages in the target queue is less than or equal to a message number threshold, and the current number of consumers of the target queue is greater than a second consumer number threshold.

[0031] In some implementations, the management configuration center is used to shut down consumers of the target queue, or schedule consumers of the target queue to other target queues with higher priority than the target queue.

[0032] It can be seen that the embodiments of the present application have the following beneficial effects:

[0033] The embodiment of the present application monitors the actual push processing time of the message in the priority queue and dynamically senses the number of timeout delay information of the queue. The number of timeout delay information can characterize the congestion of the priority queue, so the number of consumers of the priority queue is automatically adjusted based on the number of timeout delay information, so that the number of consumers of the priority queue is related to the congestion of the priority queue. In the case of congestion in the priority queue, more consumers can be called up to push the messages in the priority queue. In the case of idle priority queue, the consumers of the priority queue can be reduced to save server resources. Therefore, the embodiment of the present application can dynamically adjust the number of consumers according to the actual situation, reduce the risk of wasting server resources due to processing messages according to a fixed number of consumers, and make more full use of server resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 is a schematic diagram of a message access service provided by an embodiment of the present application;

[0035] Figure 2 is a schematic diagram of a message consumer service provided by an embodiment of the present application;

[0036] Figure 3 It is a schematic diagram of a management configuration center scheduling consumers provided by an embodiment of the present application;

[0037] Figure 4 This is a flowchart of a message push method based on multiple queues provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0039] The embodiment of the present application discloses a message push method and system based on multiple queues, the method comprising: receiving a message push request from an upstream business system; adding a request timestamp to the message body, determining the priority of the message according to the type of message and the content of the message, and placing the message into a priority queue based on the priority of the message; processing the message through a consumer, recording the processing completion timestamp of the message; obtaining the actual push processing time of the message based on the request timestamp and the processing completion timestamp of the message. Determine whether the actual push processing time of the message exceeds the processing time threshold, if the actual push processing time of the message exceeds the processing time threshold, record the timeout delay information; based on the number of timeout delay information of a priority queue recorded within a sliding time window of a predetermined duration, adjust the number of consumers of the priority queue, thereby making better use of the server resources and pushing messages more stably and efficiently.

[0040] An embodiment of the present application provides a multi-queue message push system, which includes a message access service, a management configuration center, and a message consumer service.

[0041] The message access service is used to receive push requests from upstream business systems and record request timestamps. The request timestamp indicates the time point when the message access service receives the push request. The message access service determines the priority of the message through configuration based on the content of the message and the type of the message. The message access service adds the request timestamp to the message body. Then, based on the priority of the message and the priorities of multiple queues, the message access service determines a target queue that matches the priority of the message from multiple queues, and adds the message to the target queue. In some embodiments, the number of consumers corresponding to the priority queue is positively correlated with the priority of the priority queue. For example, if the priority of a priority queue is higher, the number of consumers corresponding to the priority queue is greater, and more consumers process the messages in the priority queue, so that messages in queues with higher priorities are processed more preferentially.

[0042] The message access service is also used to periodically pull the priorities configured for various message types and message contents from the management configuration center, and store the corresponding relationship between the configured message type, message content and priority in the memory. Figure 1 shown.

[0043] The message consumer service is used to periodically pull the processing time threshold configured for each priority queue from the management configuration center and update the processing time threshold in the memory. Consumers of each priority queue consume messages in the corresponding priority queue in sequence and push the messages to the user's client. After pushing the message, the consumer records the processing completion timestamp of the message. The processing completion timestamp indicates the time point when the message push is completed.

[0044] The message consumer service obtains the actual push processing time of the message based on the request timestamp saved in the message and the message processing completion timestamp of the message. The actual push processing time is the time difference between the request timestamp and the message processing completion timestamp. The actual push processing time of the message can also be called the push delay of the message. For example, the message consumer service subtracts the request timestamp saved in the message body from the message processing completion timestamp to obtain the actual push processing time of the message. The message consumer service determines whether the actual push processing time of the message is greater than the processing time threshold configured for the priority queue. If the actual push processing time of the message is greater than the processing time threshold configured for the priority queue, it indicates that the processing speed of the messages in the priority queue is too slow. Therefore, the consumer service records the timeout delay information and sends the timeout delay information to the management configuration center. If the actual push processing time of the message is less than or equal to the processing time threshold configured for the priority queue, no processing is performed.

[0045] The timeout delay information includes the priority queue name and the current occurrence time. The current occurrence time is the time when the message consumer service determines that the actual push processing time of the message is greater than the processing time threshold configured for the priority queue. By recording the priority queue name and the current occurrence time, it is equivalent to recording which queue has a timeout delay and when.

[0046] Message consumer services such as Figure 2 As shown, generally, queues with higher priorities have more consumers.

[0047] The management configuration center is used to configure the processing time threshold of each priority queue. The processing time threshold is used to indicate the maximum time allowed for messages in the priority queue to be processed. Consumer services can pull and update the processing time threshold from the management configuration center.

[0048] In addition, the management configuration center also configures the consumer quantity thresholds of each priority queue. The consumer quantity thresholds include a first consumer quantity threshold and a second consumer quantity threshold. The first consumer quantity threshold indicates the maximum number of consumers that a priority queue can have, and the first consumer quantity threshold can also be called the maximum number of consumers. The second consumer quantity threshold indicates the minimum number of consumers that a priority queue can have, and the second consumer quantity threshold can also be called the minimum number of consumers.

[0049] In addition, the management configuration center also configures the number of times that warnings can occur. The management configuration center is also used to monitor the current number of consumers in each priority queue. The management configuration center configures the priority queues corresponding to the message type and message content for the message access service to pull and update.

[0050] For each configured priority queue, the management configuration center uses a time window sliding algorithm to count the number of timeout delay information received within a sliding time window. If the number of timeout delay information received by the management configuration center for priority queue L1 within a sliding time window of a predetermined length is greater than the configured number of warnings for priority queue L1, T1, it means that a message delay warning of excessive length has occurred in the priority queue, and the management configuration center can call up a new consumer to consume the messages of the priority queue more quickly.

[0051] In some embodiments, if the number of timeout delay information received from the priority queue L1 within the sliding window of a predetermined length is greater than the configured number of priority queue L1 warnings that can occur T1, and the number of consumers in the current priority queue is less than the configured maximum number of consumers, the management configuration center calls a new consumer to consume the message of the priority queue. Considering that the number of all consumers is limited, if consumers are added to a certain priority queue without restriction, a single priority queue may exhaust all available consumers, resulting in no available consumers to call when other priority queues are congested. Based on this, by introducing the limiting condition that the number of consumers in the current priority queue is less than the configured maximum number of consumers when calling a new consumer, the risk of the aforementioned available consumers being exhausted is reduced.

[0052] In some embodiments, if the duration during which the priority queue L1 does not generate timeout delay information (or the duration during which no message delay excessive warning occurs) is greater than or equal to the duration threshold, and the number of unconsumed messages in the priority queue L1 is less than or equal to the message number threshold, indicating that the number of consumers of the priority queue can be reduced to save server resources, the management configuration center reduces the consumers of the priority queue. Ways to reduce the consumers of a priority queue include shutting down the consumers of the queue, or scheduling the consumers of the queue to other priority queues for consumption. For example, the management configuration center schedules the consumers of the priority queue L1 to the priority queue L2, and the priority of the priority queue L2 is higher than the priority of the priority queue L1. The management configuration center schedules consumers such as Figure 3 shown.

[0053] In some embodiments, if the duration during which the priority queue L1 does not generate timeout delay information (or the duration during which the message delay warning does not occur) is greater than or equal to the duration threshold, and the number of unconsumed messages in the priority queue is less than or equal to the message number threshold, and the current number of consumers in the priority queue is greater than the configured second consumer number threshold (minimum number of consumers), the management configuration center reduces the consumers of the priority queue. Considering that if the current number of consumers in the priority queue is less than the configured minimum number of consumers, when the message corresponding to the priority queue is subsequently received, it is usually necessary to call up a new consumer to process the message corresponding to the priority queue, resulting in a greater delay in message processing. Based on this, when reducing the consumers of the priority queue, the limiting condition that the current number of consumers in the priority queue is greater than the configured minimum number of consumers is introduced, thereby reducing the delay caused by calling up new consumers.

[0054] This embodiment monitors the message push delay of the priority queue through the management configuration center, and dynamically senses whether the priority queue has a message delay warning based on the number of timeout delay information. If a priority queue has a message delay warning (the number of timeout delay information is greater than the number of times the warning of the priority queue can occur), it indicates that congestion has occurred in the queue. By automatically calling new consumers to consume the messages in the priority queue, the messages in the priority queue can be pushed faster without the need for manual operation to adjust the number of consumers, thereby improving the timeliness of message push; if there is no message delay warning for a long time (the duration of no timeout delay information is greater than or equal to the duration threshold) and the number of unconsumed messages in the priority queue is less than or equal to a certain number, the number of consumers in the priority queue can be automatically reduced to save server resources.

[0055] Please refer to the attached Figure 4 , attached Figure 4 This is a flowchart of a message push method based on multiple queues provided in an embodiment of the present application, Figure 4 The method is applied to a computer device, in which a Figure 1 The message access service shown, Figure 3 The management configuration center shown and Figure 2 The message consumer service shown in the figure, the computer device executes the attached Figure 4 The method shown. Figure 4 The method shown includes the following steps.

[0056] S410, receiving a push request, where the push request indicates pushing a message to a client.

[0057] S420, adding a request timestamp to the message, and based on the priority of the message, adding the message to a target queue in a plurality of priority queues that matches the priority of the message, wherein the request timestamp indicates the time point when the push request is received.

[0058] S430: The consumer consumes the message in the target queue and pushes the message to the client.

[0059] S440, recording the processing completion timestamp of the message, where the processing completion timestamp indicates the time point when the message push is completed.

[0060] S450, based on the request timestamp stored in the message and the message processing completion timestamp of the message, obtain the actual push processing time of the message, where the actual push processing time is the time difference between the request timestamp and the message processing completion timestamp.

[0061] S460: If the actual push processing time of the message is greater than the processing time threshold corresponding to the target queue, the timeout delay information of the target queue is recorded.

[0062] S470: Adjust the number of consumers of the target queue based on the number of timeout delay information of the target queue recorded within a sliding time window of a predetermined length.

[0063] This embodiment dynamically senses the number of timeout delay information of the queue by monitoring the actual push processing time of the message in the priority queue. The number of timeout delay information can characterize the congestion of the priority queue, so the number of consumers of the priority queue is automatically adjusted based on the number of timeout delay information, so that the number of consumers of the priority queue is related to the congestion of the priority queue. In the case of congestion in the priority queue, more consumers can be called up to push the messages in the priority queue. In the case of idle priority queue, the consumers of the priority queue can be reduced to save server resources. Therefore, the embodiment of the present application can dynamically adjust the number of consumers according to the actual situation, reducing the risk of wasting server resources due to processing messages according to a fixed number of consumers, thereby making more full use of server resources.

[0064] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referenced to each other, and each embodiment focuses on the differences from other embodiments.

[0065] A refers to B, which means that A is the same as B or A is a simple variant of B.

[0066] The terms "first" and "second" in the description and claims of the embodiments of the present application are used to distinguish different objects, rather than to describe the specific order of the objects, and cannot be understood as indicating or implying relative importance. For example, the first consumer number threshold and the second consumer number threshold are used to distinguish different consumer number thresholds, rather than to describe the specific order of the consumer number thresholds, and cannot be understood as the first consumer number threshold being more important than the second consumer number threshold.

[0067] In the embodiments of the present application, unless otherwise specified, “at least one” means one or more, and “plurality” means two or more.

[0068] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in accordance with the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk SolidState Disk (SSD)), etc.

[0069] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A message push method based on multiple queues, characterized in that: The method comprises: receiving a push request, wherein the push request indicates that a message is pushed to a client; adding a request timestamp to the message, and adding the message to a target queue that matches the priority of the message among multiple priority queues based on the priority of the message, wherein the request timestamp indicates a time point when the push request is received; Consume the message in the target queue through a consumer, and push the message to the client; Recording the processing completion timestamp of the message, where the processing completion timestamp indicates the time point when the message push is completed; Based on the request timestamp stored in the message and the message processing completion timestamp of the message, obtaining the actual push processing time of the message, the actual push processing time being the time difference between the request timestamp and the message processing completion timestamp; If the actual push processing time of the message is greater than the processing time threshold corresponding to the target queue, record the timeout delay information of the target queue; The number of consumers of the target queue is adjusted based on the amount of timeout delay information of the target queue recorded within a sliding time window of a predetermined length.

2. The method according to claim 1, characterized in that The adjusting the number of consumers of the target queue based on the number of timeout delay information of the target queue recorded within the sliding time window of a predetermined length includes: If the number of timeout delay information of the target queue recorded within a sliding time window of a predetermined length is greater than the number of warnings that can occur for the target queue, increase the number of consumers of the target queue and schedule the newly added consumers to consume messages in the target queue.

3. The method according to claim 1, characterized in that: The adjusting the number of consumers of the target queue based on the number of timeout delay information of the target queue recorded within the sliding time window of a predetermined length includes: If the number of timeout delay information of the target queue recorded within a sliding time window of a predetermined length is greater than the number of warnings that can occur for the target queue, and the current number of consumers of the target queue is less than the first consumer number threshold, increase the number of consumers of the target queue and schedule the newly added consumers to consume messages in the target queue.

4. The method according to claim 1, characterized in that: The adjusting the number of consumers of the target queue based on the number of timeout delay information of the target queue recorded within the sliding time window of a predetermined length includes: If the duration for which the target queue does not generate timeout delay information is greater than or equal to the duration threshold, and the number of unconsumed messages in the target queue is less than or equal to the message number threshold, reduce the number of consumers of the target queue.

5. The method according to claim 1, characterized in that The adjusting the number of consumers of the target queue based on the number of timeout delay information of the target queue recorded within the sliding time window of a predetermined length includes: If the duration of no timeout delay information in the target queue is greater than or equal to the duration threshold, and the number of unconsumed messages in the target queue is less than or equal to the message number threshold, and the current number of consumers of the target queue is greater than the second consumer number threshold, reduce the number of consumers in the target queue.

6. The method according to claim 4 or 5, characterized in that: The reducing the consumers of the target queue comprises: Close the consumer of the target queue, or schedule the consumer of the target queue to another target queue with a higher priority than the target queue.

7. A message push system based on multiple queues, characterized in that: The system comprises: A message access service, for receiving a push request, the push request indicating a message to be pushed to a client; adding a request timestamp to the message, and adding the message to a target queue that matches the priority of the message among multiple priority queues based on the priority of the message, the request timestamp indicating a time point when the push request is received; A message consumer service is used to consume the message in the target queue through a consumer and push the message to the client; record the processing completion timestamp of the message, the processing completion timestamp indicates the time point when the message push is completed; based on the request timestamp saved in the message and the message processing completion timestamp of the message, obtain the actual push processing time of the message, the actual push processing time is the time difference between the request timestamp and the message processing completion timestamp; if the actual push processing time of the message is greater than the processing time threshold corresponding to the target queue, record the timeout delay information of the target queue, and send the timeout delay information to the management configuration center; The management configuration center is used to adjust the number of consumers of the target queue based on the amount of timeout delay information of the target queue recorded within a sliding time window of a predetermined length.

8. The system according to claim 7, characterized in that The management configuration center is used to increase consumers of the target queue and schedule the newly added consumers to consume messages in the target queue if the number of timeout delay information of the target queue recorded within a sliding time window of a predetermined length is greater than the number of times an early warning of the target queue can occur.

9. The system according to claim 7, characterized in that The management configuration center is used to increase consumers of the target queue and schedule the newly added consumers to consume messages in the target queue if the number of timeout delay information of the target queue recorded within a sliding time window of a predetermined length is greater than the number of warnings that can occur for the target queue, and the current number of consumers of the target queue is less than a first consumer number threshold.

10. The system according to claim 7, characterized in that The management configuration center is used to reduce the consumers of the target queue if the duration for which the target queue does not generate timeout delay information is greater than or equal to a duration threshold, and the number of unconsumed messages in the target queue is less than or equal to a message quantity threshold.

Images