Event overflow handling by coalescing and updating previously-queued event notification

• US 9,201,715 B2
• Filed: 03/22/2012
• Issued: 12/01/2015
• Est. Priority Date: 09/10/2010
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Jennings, Cheryl L., Mishra, Rajeev, Nayar, Trishali, Russell, Lance W.
• Primary Examiner(s): Sough, H S
• Assistant Examiner(s): Yun, Carina
• Application Number:
  US13/427,159
• Publication Number:
  US 20120198477A1
• Time in Patent Office: 1,349 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 2209/546 Xcast
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

An event notification method for distributed processing systems provides reduction of queue space and event processing bandwidth associated with duplicate events such as a particular event that is duplicated and results in multiple event notifications propagated for multiple consumers. When a duplicate event notification is received at an input to an event notification queue, rather than queuing the duplicate event notification, a sequence number of the event notification already in the queue is updated to indicate to the event consumer, exactly how many duplicate events have been received. The timestamp of the updated event notification may also be set to the timestamp of the most recently received duplicate event notification.

Claims

1. A method for event notification within a computer system processing cluster comprising a plurality of physical or virtual processing modes, the method comprising:

receiving event notifications corresponding to events occurring on one or more of the processing nodes;

queuing the received event notifications in one or more queues for delivery to event consumers;

coalescing duplicate event notifications in a single resulting event notification, wherein the event notifications contain a event sequence number stored therein, wherein the coalescing further increments the event sequence number by modifying the event sequence number stored in the single resulting event notification to yield a modified event notification that, when provided to one of the event consumers indicates to the one of the event consumers, a total number of original and duplicate events that have been received, and wherein the coalescing further modifies a timestamp stored in the single resulting event notification to match a timestamp stored in a most recent one of the duplicate event notifications, by reading the timestamp of the most recent one of the duplicate event notifications and writing a value of the timestamp of the most recent one of the duplicate event notifications to a storage location of the timestamp stored in the single resulting event notification; and

at the event consumer, determining whether the event notifications have been duplicated one or more times by reading the event sequence number stored in the event notifications to determine whether the event notifications have been modified to indicate the total number of original and duplicate events that have been received.

2. The method of claim 1, wherein the coalescing only coalesces sequential duplicate events.

3. The method of claim 2, wherein the coalescing comprises:

responsive to the receiving having received an event notification;

peeking in a corresponding queue to determine whether a most recently queued event notification is a duplicate of the received event notification;

responsive to the peeking determining that the most recently queued event notification is not a duplicate of the received event notification, queuing the event notification in the corresponding queue without altering the sequence number of the event notification; and

responsive to the peeking determining that the most recently queued event notification is a duplicate of the received event notification, incrementing the sequence number of the most recently queued event notification without queuing the received event notification in the queue.

4. The method of claim 3, further responsive to the peeking determining that the most recently queued event notification is a duplicate of the received event notification, updating a timestamp of the most recently queued event notification.

5. The method of claim 1, wherein the modifying of the timestamp is performed selectively in response to a predetermined setting that directs the coalescing to update event notification timestamps, wherein if the predetermined setting is not set, the coalescing does not modify the timestamp of the single resulting event notification to match the timestamp of the most recent of the duplicate event notifications.

6. The method of claim 1, wherein the event notifications are received as callbacks to an application programming interface provided by the file system that implements at least a portion of the event notification method, and wherein the queuing is performed in response to receiving the callbacks.

7. The method of claim 5, further comprising:

during registration by the event consumer to receive notification of events of a given event type, specifying a flag that indicates for the given event type and the event consumer, whether the timestamps of coalesced event notifications of the given event type and for the event consumer are to be updated with the timestamp of received event notifications, or whether original timestamps should be preserved, wherein the coalescing only modifies the timestamp stored in the single resulting event notification if a flag corresponding to an event type and event consumer of the single resulting event notification has been previously set during registration of the event consumer.

8. A computer system comprising a processing cluster including a plurality of physical or virtual processing nodes, the computer system comprising at least one processor configured to execute program instructions and at least one memory coupled to the processor and storing the program instructions, wherein the program instructions are program instructions that provide event notification within the computer system, the program instructions comprising:

program instructions that receive event notifications corresponding to events occurring on one or more of the processing nodes;

program instructions that queue the received event notifications in one or more queues for delivery to event consumers;

program instructions that coalesce duplicate event notifications in a single resulting event notification, wherein the event notifications contain an event sequence number stored therein, wherein the program instructions that coalesce further increment the event sequence number by modifying the event sequence number stored in the single resulting event notification to yield a modified event notification that, when provided to one of the event consumers indicates to the one of the event consumers, a total number of original and duplicate events that have been received, and wherein the program instructions that coalesce further comprise program instructions that modify a timestamp stored in the single resulting event notification to match a timestamp stored in a most recent one of the duplicate event notifications, by reading the timestamp of the most recent one of the duplicate event notifications and writing a value of the timestamp of the most recent one of the duplicate event notifications to a storage location of the timestamp stored in the single resulting event notification; and

program instructions that, at the event consumer, determine whether the event notifications have been duplicated one or more times by reading the event sequence number stored in the event notifications to determine whether the event notifications have been modified to indicate the total number of original and duplicate events that have been received.

9. The computer system of claim 8, wherein the program instructions that coalesce comprise program instructions that only coalesce sequential duplicate events.

10. The computer system of claim 9, wherein the program instructions that coalesce comprise:

program instructions that, responsive to the program instructions that receive having received an event notification, peek in a corresponding queue to determine whether a most recently queued event notification is a duplicate of the received event notification;

program instructions that, responsive to the program instructions that peek having determined that the most recently queued event notification is not a duplicate of the received event notification, queue the event notification in the corresponding queue without altering the sequence number of the event notification; and

program instructions that, responsive to the program instructions that peek to having determined that the most recently queued event notification is a duplicate of the received event notification, increment the sequence number of the most recently queued event notification without queuing the received event notification in the queue.

11. The computer system of claim 10, further comprising program instructions that, responsive to the program instructions that peek having determine that the most recently queued event notification is a duplicate of the received event notification, update a timestamp of the most recently queued event notification.

12. The computer system of claim 8, wherein the program instructions that modify a timestamp are selectively executed in response to a predetermined setting that directs the program instructions for coalescing to update event notification timestamps, wherein if the predetermined setting is not set, the program instructions that coalesce do not modify the timestamp of the single resulting event notification to match the timestamp of the most recent of the duplicate event notifications.

13. The computer system of claim 12, wherein the program instructions further comprise program instructions that, during registration by the event consumer to receive notifications of events of a given event type, specify a flag that indicates for the given event type and the event consumer, whether the timestamps of coalesced event notifications of the given event type and for the event consumer are to be updated with the timestamp of received event notifications, or whether original timestamps should be preserved, wherein the program instructions that coalesce only modify the timestamp stored in the single resulting event notification if a flag corresponding to an event type and event consumer of the single resulting event notification has been previously set during registration of the event consumer.

14. The computer system of claim 8, wherein the event notifications are received as callbacks to an application programming interface provided by the file system that implements at least a portion of the event notification method, and wherein the program instructions for queuing are executed in response to receiving the callbacks.

15. A computer program product comprising a computer-readable memory device storing program instructions for execution within a computer system, the computer system comprising a processing cluster including a plurality of physical or virtual processing modes, wherein the program instructions are program instructions that provide event notification within the computer system, the program instructions comprising:

program instructions that receive event notifications corresponding to events occurring on one or more of the processing nodes;

program instructions that queue the received event notifications in one or more queues for delivery to event consumers;

program instructions that coalesce duplicate event notifications in a single resulting event notification, wherein the event notifications contain an event sequence number stored therein, wherein the program instructions that coalesce further increment the event sequence number by modifying the event sequence number stored in the single resulting event notification to yield a modified event notification that, when provided to one of the event consumers indicates to the one of the event consumers, a total number of original and duplicate events that have been received, and wherein the program instructions that coalesce further comprise program instructions that modify a timestamp stored in the single resulting event notification to match a timestamp stored in a most recent one of the duplicate event notifications, by reading the timestamp of the most recent one of the duplicate event notifications and writing a value of the timestamp of the most recent one of the duplicate event notifications to a storage location of the timestamp stored in the single resulting event notification; and

program instructions that, at the event consumer, determine whether the event notifications have been duplicated one or more times by reading the event sequence number stored in the event notifications to determine whether the event notifications have been modified to indicate the total number of original and duplicate events that have been received.

16. The computer program product of claim 15, wherein the program instructions that coalesce comprise program instructions that only coalesce sequential duplicate events.

17. The computer program product of claim 16, wherein the program instructions that coalesce comprise:

program instructions that, responsive to the program instructions that receive having received an event notification, peek in a corresponding queue to determine whether a most recently queued event notification is a duplicate of the received event notification;

program instructions that, responsive to the program instructions that peek having determined that the most recently queued event notification is not a duplicate of the received event notification, queue the event notification in the corresponding queue without altering the sequence number of the event notification; and

program instructions that, responsive to the program instructions that peek to having determined that the most recently queued event notification is a duplicate of the received event notification, increment the sequence number of the most recently queued event notification without queuing the received event notification in the queue.

18. The computer program product of claim 15, wherein the program instructions that modify a timestamp are selectively executed in response to a predetermined setting that directs the program instructions for coalescing to update event notification timestamps, wherein if the predetermined setting is not set, the program instructions that coalesce do not set the timestamp of the single resulting event notification to match the timestamp of the most recent of the duplicate event notifications.

19. The computer program product of claim 15, wherein the event notifications are received as callbacks to an application programming interface provided by the file system that implements at least a portion of the event notification method, and wherein the program instructions for queuing are executed in response to receiving the callbacks.

20. The computer program product of claim 18, wherein the program instructions further comprise program instructions that, during registration by the event consumer to receive notifications of events of a given event type, specify a flag that indicates for the given event type and the event consumer, whether the timestamps of coalesced event notifications of the given event type and for the event consumer are to be updated with the timestamp of received event notifications, or whether original timestamps should be preserved, wherein the program instructions that coalesce only modify the timestamp stored in the single resulting event notification if a flag corresponding to an event type and event consumer of the single resulting event notification has been previously set during registration of the event consumer.