Method and apparatus for recovering from a failure in a distributed event notification system

• US 20040123183A1
• Filed: 12/23/2002
• Published: 06/24/2004
• Est. Priority Date: 12/23/2002
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Tripathi, Ashutosh, Hisgen, Andrew L., Solter, Nicholas A., Rattner, Martin Henry
• Application Number:
  US10/329,011
• Publication Number:
  US 20040123183A1
• Time in Patent Office: Days
• US Class Current: 714/31
• CPC Class Codes: H04L 1/22 using redundant apparatus to increase reliability

Abstract

One embodiment of the present invention provides a system that facilitates recovering from failure in a distributed event notification system. During operation, the system detects a failure of an event forwarder, which notifies subscribers of events generated by distributed components in the distributed computing system. In response to detecting the failure, the system restarts the event forwarder, typically on another node in the distributed computing system. Next, the system requests a snapshot of current state from the distributed components. In response to this request, the system subsequently receives events from the distributed components that specify current state of the distributed components, and then forwards the events to subscribers that are registered to be notified of the events.

Claims

1. A method for recovering from a failure in a distributed event notification system within a distributed computing system, comprising:

detecting a failure of an event forwarder, which notifies subscribers of events generated by distributed components in the distributed computing system, wherein the event forwarder is part of the distributed event notification system;

restarting the event forwarder;

requesting a snapshot of current state from the distributed components;

in response to the request, receiving events from the distributed components that specify current state of the distributed components; and

forwarding the events to subscribers that are registered to be notified of the events.

2. The method of claim 1, wherein the events that specify the current state of the distributed components are received at the event forwarder through normal event notification channels.

3. The method of claim 1, wherein cluster membership events received from the distributed components include incarnation numbers for the underlying nodes of the distributed components, wherein the incarnation numbers allow subscribers to determine if a given underlying node has changed since the last time an event was received from the given underlying node.

4. The method of claim 1, wherein events generated by the distributed components are associated with changes of state in the distributed components.

5. The method of claim 4, wherein events generated by the distributed components provide snapshots of current state information for the distributed components, instead of merely providing incremental state changes.

6. The method of claim 1, wherein the distributed components can include:

nodes in the distributed computing system;

applications running on nodes in the distributed computing system; and

application components running on nodes in the distributed computing system.

7. The method of claim 1, wherein an 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;

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

a state change related to application monitoring.

8. The method of claim 1, wherein the subscribers can include:

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

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

18. The apparatus of claim 7, wherein the events that specify the current state of the distributed components are received at the event forwarder through normal event notification channels.

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

detecting a failure of an event forwarder, which notifies subscribers of events generated by distributed components in the distributed computing system, wherein the event forwarder is part of the distributed event notification system;

restarting the event forwarder;

requesting a snapshot of current state from the distributed components;

in response to the request, receiving events from the distributed components that specify current state of the distributed components; and

forwarding the events to subscribers that are registered to be notified of the events.

10. The computer-readable storage medium of claim 9, wherein the events that specify the current state of the distributed components are received at the event forwarder through normal event notification channels.

11. The computer-readable storage medium of claim 9, wherein cluster membership events received from the distributed components include incarnation numbers for the underlying nodes of the distributed components, wherein the incarnation numbers allow subscribers to determine if a given underlying node has changed since the last time an event was received from the given underlying node.

12. The computer-readable storage medium of claim 9, wherein events generated by the distributed components are associated with changes of state in the distributed components.

13. The computer-readable storage medium of claim 12, wherein events generated by the distributed components provide snapshots of current state information for the distributed components, instead of merely providing incremental state changes.

14. The computer-readable storage medium of claim 9, wherein the distributed components can include:

nodes in the distributed computing system;

applications running on nodes in the distributed computing system; and

application components running on nodes in the distributed computing system.

15. The computer-readable storage medium of claim 9, wherein an 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;

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

a state change related to application monitoring.

16. The computer-readable storage medium of claim 9, wherein the subscribers can include:

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

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

17. An apparatus that facilitates recovering from a failure in a distributed event notification system within a distributed computing system, comprising:

a detection mechanism configured to detect a failure of an event forwarder, which notifies subscribers of events generated by distributed components in the distributed computing system, wherein the event forwarder is part of the distributed event notification system;

a restarting mechanism configured to restart the event forwarder;

a requesting mechanism configured to request a snapshot of current state from the distributed components;

a receiving mechanism configured to receive events from the distributed components that specify current state of the distributed components; and

a forwarding mechanism configured to forward the events to subscribers that are registered to be notified of the events.

19. The apparatus of claim 17, wherein cluster membership events received from the distributed components include incarnation numbers for the underlying nodes of the distributed components, wherein the incarnation numbers allow subscribers to determine if a given underlying node has changed since the last time an event was received from the given underlying node.

20. The apparatus of claim 17, wherein events generated by the distributed components are associated with changes of state in the distributed components.

21. The apparatus of claim 20, wherein events generated by the distributed components provide snapshots of current state information for the distributed components, instead of merely providing incremental state changes.

22. The apparatus of claim 17, wherein the distributed components can include:

nodes in the distributed computing system;

applications running on nodes in the distributed computing system; and

application components running on nodes in the distributed computing system.

23. The apparatus of claim 17, wherein an 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;

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

a state change related to application monitoring.

24. The apparatus of claim 17, wherein the subscribers can include:

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

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