System and method of maintaining an enqueue rate of data messages into a set of queues

• US 9,432,445 B1
• Filed: 05/17/2013
• Issued: 08/30/2016
• Est. Priority Date: 05/17/2013
• Status: Active Grant

• Current Assignee: T-Mobile Innovations LLC (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Leonard, Mark D.
• Primary Examiner(s): Bates, Kevin
• Assistant Examiner(s): Naoreen, Nazia
• Application Number:
  US13/897,220
• Time in Patent Office: 1,201 Days
• Field of Search: 709/219
• US Class Current: 1/1
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30

Abstract

A system comprises a component which receives an initial status message, from a primary queue manager, comprising a rate of data messages moving into a primary queue. The component detects that a primary queue rate is below a predetermined range based on the received initial status message. The component increases the weight of the primary queue in response to detecting that the primary queue rate provided by the initial status message is below the predetermined range. The component receives a subsequent status message, from the primary queue manager, comprising the rate of data messages moving into the primary queue. The component detects that the primary queue has a rate below the predetermined range based on the received subsequent status message. The component activates a secondary queue in response to detecting that the primary queue rate provided by the subsequent status message is below the predetermined range.

Claims

1. A system for maintaining an enqueue rate of data messages into a set of queues, the system comprising:

a server coupled to a cluster of primary servers and a cluster of secondary servers, the server comprising;

a processor coupled to a non-transitory memory storing a cluster server repository component stored as a set of computer instructions that upon execution by the processor configures the server to;

receive an initial status message, from a primary queue manager executing from non-transitory memory in the cluster of primary servers, comprising the enqueue rate of data messages moving into a primary queue of the primary queue manager,

detect that the primary queue has an enqueue rate below a predetermined range based on the received initial status message,

increase a weight of the primary queue in response to detecting that the enqueue rate of the primary queue provided by the initial status message is below the predetermined range,

receive a subsequent status message, from the primary queue manager, comprising the enqueue rate of data messages moving into the primary queue after the weight of the primary queue is increased,

detect that the primary queue has an enqueue rate below the predetermined range based on the received subsequent status message, and

activate, in the cluster of secondary servers, a secondary queue of a secondary queue manager in response to detecting that the enqueue rate of the primary queue provided by the subsequent status message is below the predetermined range, wherein the secondary queue manager executes from non-transitory memory in the cluster of secondary servers.

2. The system of claim 1, wherein activating the secondary queue comprises directing data messages to the second queue at an enqueue rate within the predetermined range.

3. The system of claim 2, wherein directing data messages comprises sending a directing message to a front end queue manager directing the front end queue manager to send at least some data messages from a front end queue of the front end queue manager to the secondary queue.

4. The system of claim 1, wherein increasing the weight of the primary queue comprises setting the enqueue rate above the predetermined range so that the actual enqueue rate reaches the predetermined range.

5. The system of claim 1, wherein activating the secondary queue comprises sending a weight message to the secondary queue manager of the secondary queue assigning an average weight of the primary queues to the secondary queue.

6. The system of claim 1, wherein a remote application server monitors the enqueue rate of data messages into each primary queue of a plurality of primary queues and sends an enqueue rate message to each primary queue manager of each primary queue.

7. The system of claim 1, wherein the enqueue rate comprises the number of messages moving into a queue per minute.

8. The system of claim 1, wherein the server is further configured by the cluster server repository component to:

detect that the primary queue has an enqueue rate above a predetermined range based on the received initial status message,

decrease the enqueue rate of the primary queue in response to detecting that the enqueue rate of the primary queue provided by the initial status message is above the predetermined range, wherein the enqueue rate is decreased by decreasing the weight of the primary queue,

receive a different status message, from the primary queue manager, comprising the enqueue rate of data messages moving into the primary queue,

detect that the primary queue has an enqueue rate within the predetermined range while the weight of the primary queue is below a threshold, wherein detecting is based on the received different status message, and

activate the secondary queue of the secondary queue manager in response to detecting that the enqueue rate of the primary queue is within the predetermined range while the weight of the primary queue is below the threshold.

9. The system of claim 8, wherein decreasing the weight of the primary queue balances the enqueue rate between the primary queue and one or more additional primary queues.

10. The system of claim 1, wherein the cluster server repository configures the server to activate the secondary queue of the secondary queue manager in response to detecting that the enqueue rate of the primary queue provided by the subsequent status message is below the predetermined range for a period of time.

11. A method of maintaining an enqueue rate of data messages into a set of queues, the method comprising:

receiving, by a server executing a cluster server repository component from non-transitory memory, an initial status message from a primary queue manager executing from non-transitory memory in a cluster of primary servers, the initial status message comprising the enqueue rate of data messages moving into a primary queue of the primary queue manager;

detecting, by the server executing the cluster server repository component, that the primary queue has an enqueue rate below a predetermined range based on the received initial status message;

increasing, by the server executing the cluster server repository component, a weight of the primary queue in response to detecting that the enqueue rate of the primary queue provided by the initial status message is below the predetermined range;

receiving, by the server executing the cluster server repository component, a subsequent status message, from the primary queue manager, comprising the enqueue rate of data messages moving into the primary queue after the weight of the primary queue is increased;

detecting, by the server executing the cluster server repository component, that the primary queue has an enqueue rate below the predetermined range based on the received subsequent status message; and

activating, in a cluster of secondary servers by the server executing the cluster server repository component, a secondary queue of a secondary queue manager in response to detecting that the enqueue rate of the primary queue provided by the subsequent status message is below the predetermined range, wherein the secondary queue manager executes from non-transitory memory in the cluster of secondary servers.

12. The method of claim 11, further comprising directing, by the cluster server repository, data messages to the second queue at an enqueue rate within the predetermined range, wherein directing data messages comprises sending a directing message to a front end queue manager directing the front end queue manager to send at least some data messages from a front end queue of the front end queue manager to the secondary queue.

13. The method of claim 11, wherein increasing the weight of the primary queue comprises setting the enqueue rate above the predetermine range so that the actual enqueue rate reaches the predetermined range.

14. The method of claim 11, wherein detecting based on the received initial status message comprises detecting, by the cluster server repository, that the enqueue rate of the primary queue is below a predetermined range for a predetermined amount of time.

15. The method of claim 11, wherein the subsequent status message is received by the cluster server repository after a predetermine period of time beginning at the time the initial status message was received by the cluster server repository.

16. A method of maintaining an enqueue rate of data messages into a set of queues, the method comprising:

receiving, by a server executing a cluster server repository component from non-transitory memory, an initial status message from a primary queue manager executing from non-transitory memory in a cluster of primary servers, the initial status message comprising the enqueue rate of data messages moving into a primary queue of the primary queue manager;

detecting, by the server executing the cluster server repository component, that the primary queue has an enqueue rate above a predetermined range based on the received initial status message;

decreasing, by the server executing the cluster server repository component, the enqueue rate of the primary queue in response to detecting that the enqueue rate of the primary queue provided by the initial status message is above the predetermined range;

receiving, by the server executing the cluster server repository component, a subsequent status message, from the primary queue manager, comprising the enqueue rate of data messages moving into the primary queue;

detecting, by the server executing the cluster server repository component based on the received subsequent status message, that the primary queue has an enqueue rate within the predetermined range while a weight of the primary queue is below a threshold; and

activating, in a cluster of secondary servers by the server executing the cluster server repository component, a secondary queue of a secondary queue manager in response to detecting that the enqueue rate of the primary queue is within the predetermined range while the weight of the primary queue is below the threshold, wherein the secondary queue manager executes from non-transitory memory in the cluster of secondary servers.

17. The method of claim 16, wherein decreasing the enqueue rate of the primary queue balances the enqueue rate between the primary queue and one or more additional primary queues.

18. The method of claim 16, wherein detecting based on the received initial status message comprises detecting, by the cluster server repository, that the enqueue rate of the primary queue is above a predetermined range for a predetermined amount of time.

19. The method of claim 16, wherein the subsequent status message is received by the cluster server repository after a predetermine period of time beginning at the time the initial status message was received by the cluster server repository.

20. The method of claim 16, wherein the subsequent status message comprises the weight of the primary queue.