Method and apparatus for providing a highly available distributed event notification mechanism

• US 20040088401A1
• Filed: 10/31/2002
• Published: 05/06/2004
• Est. Priority Date: 10/31/2002
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Hisgen, Andrew L., Tripathi, Ashutosh, Solter, Nicholas A.
• Application Number:
  US10/285,176
• Publication Number:
  US 20040088401A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• 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 69/329 in the application layer [OSI layer 7]

Abstract

One embodiment of the present invention provides a system that supports event notification within a distributed computing system. Upon receiving an event that was generated at a node in the distributed computing system, the system performs a lookup in a database to determine a list of clients that are registered to be notified of the event. The system then sends a notification of the event to clients in the list. In a variation on this embodiment, the event notification is performed by an event forwarding mechanism that is highly available. In this way, if the event forwarding mechanism fails, a new instance of the event forwarding mechanism is automatically started, possibly on a different node within the distributed computing system.

Claims

1. A method for providing event notification within a distributed computing system, comprising:

receiving an event that was generated at a node in the distributed computing system;

in response to receiving the event,

looking up a list of clients that are registered to be notified of the event in a database, and

sending a notification of the event to clients in the list of clients.

2. The method of claim 1, wherein the event is received at an event forwarding mechanism that is highly available, whereby if the event forwarding mechanism fails, a new instance of the event forwarding mechanism is automatically started, possibly on a different node within the distributed computing system.

3. The method of claim 1, wherein the list of clients can include:

applications or application components running within the distributed computing system; and

applications or application components running outside of the distributed computing system.

4. The method of claim 1, wherein the event can include:

a node joining a cluster in the distributed computing system;

a node leaving the cluster in the distributed computing system;

a state change related to an application or an application component running within the distributed computing system; and

a state change for a group of related applications running within the distributed computing system.

5. The method of claim 4, wherein the state change related to the application can include:

the application entering an on-line state;

the application entering an off-line state;

the application entering a degraded state, wherein the application is not functioning efficiently;

the application entering a faulted state, wherein the application is not functioning;

application monitoring started; and

application monitoring stopped.

6. The method of claim 1, further comprising:

receiving a registration request from a client;

wherein the registration request includes a callback address for the client and a list of events that the client wants to be notified of; and

in response to the registration request, recording the callback address of the client and the list of events in the database, so that the client can be notified if events in the list occur.

7. The method of claim 1, further comprising distributing the event through an inter-node event forwarding mechanism to other nodes in the distributed computing system.

8. The method of claim 1, wherein generating the event involves posting the event through an application programming interface (API) provided by the distributed computing system.

9. The method of claim 1, wherein the event is received across a network that couples together nodes in the distributed computing system.

10. The method of claim 1, wherein the database is a fault-tolerant distributed database.

11. A computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for providing event notification within a distributed computing system, the method comprising:

receiving an event that was generated at a node in the distributed computing system;

in response to receiving the event,

looking up a list of clients that are registered to be notified of the event in a database, and

sending a notification of the event to clients in the list of clients.

12. The computer-readable storage medium of claim 11, wherein the event is received at an event forwarding mechanism that is highly available, whereby if the event forwarding mechanism fails, a new instance of the event forwarding mechanism is automatically started, possibly on a different node within the distributed computing system.

13. The computer-readable storage medium of claim 11, wherein the list of clients can include:

applications or application components running within the distributed computing system; and

applications or application components running outside of the distributed computing system.

14. The computer-readable storage medium of claim 11, wherein the event can include:

a node joining a cluster in the distributed computing system;

a node leaving the cluster in the distributed computing system;

a state change related to an application or an application component running within the distributed computing system; and

a state change for a group of related applications running within the distributed computing system.

15. The computer-readable storage medium of claim 14, wherein the state change related to the application can include:

the application entering an on-line state;

the application entering an off-line state;

the application entering a degraded state, wherein the application is not functioning efficiently;

the application entering a faulted state, wherein the application is not functioning;

application monitoring started; and

application monitoring stopped.

16. The computer-readable storage medium of claim 11, wherein the method further comprises:

receiving a registration request from a client;

wherein the registration request includes a callback address for the client and a list of events that the client wants to be notified of; and

in response to the registration request, recording the callback address of the client and the list of events in the database, so that the client can be notified if events in the list occur.

17. The computer-readable storage medium of claim 11, wherein the method further comprises distributing the event through an inter-node event forwarding mechanism to other nodes in the distributed computing system.

18. The computer-readable storage medium of claim 11, wherein generating the event involves posting the event through an application programming interface (API) provided by the distributed computing system.

19. The computer-readable storage medium of claim 11, wherein the event is received across a network that couples together nodes in the distributed computing system.

20. The computer-readable storage medium of claim 11, wherein the database is a fault-tolerant distributed database.

21. An apparatus that provides event notification within a distributed computing system, comprising:

a receiving mechanism configured to receive an event that was generated at a node in the distributed computing system;

a notification mechanism configured to,

look up a list of clients that are registered to be notified of the event in a database, and to

send a notification of the event to clients in the list of clients.

22. The apparatus of claim 21, wherein the receiving mechanism and the notification mechanism are part of an event forwarding mechanism that is highly available, whereby if the event forwarding mechanism fails, a new instance of the event forwarding mechanism is automatically started, possibly on a different node within the distributed computing system.

23. The apparatus of claim 21, wherein the list of clients can include:

applications or application components running within the distributed computing system; and

applications or application components running outside of the distributed computing system.

24. The apparatus of claim 21, wherein the event can include:

a node joining a cluster in the distributed computing system;

a node leaving the cluster in the distributed computing system;

a state change related to an application or an application component running within the distributed computing system; and

a state change for a group of related applications running within the distributed computing system.

25. The apparatus of claim 24, wherein the state change related to the application can include:

the application entering an on-line state;

the application entering an off-line state;

the application entering a degraded state, wherein the application is not functioning efficiently;

the application entering a faulted state, wherein the application is not functioning;

application monitoring started; and

application monitoring stopped.

26. The apparatus of claim 21, further comprising a registration mechanism configured to receive a registration request from a client, wherein the registration request includes a callback address for the client and a list of events that the client wants to be notified of;

wherein in response to the registration request, the registration mechanism is configured to record the callback address of the client and the list of events in the database, so that the client can be notified if events in the list occur.

27. The apparatus of claim 21, further comprising an inter-node event forwarding mechanism configured to distribute the event to other nodes in the distributed computing system.

28. The apparatus of claim 21, wherein the receiving mechanism is configured to receive an event that was posted through an application programming interface (API) provided by the distributed computing system.

29. The apparatus of claim 21, wherein the receiving mechanism is configured to receive the event across a network that couples together nodes in the distributed computing system.

30. The apparatus of claim 21, wherein the database is a fault-tolerant distributed database.