RESTARTING EVENT AND ALERT ANALYSIS AFTER A SHUTDOWN IN A DISTRIBUTED PROCESSING SYSTEM

• US 20130073726A1
• Filed: 11/15/2012
• Published: 03/21/2013
• Est. Priority Date: 06/22/2011
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: CAREY, JAMES E., MARKLAND, MATTHEW W., SANDERS, PHILIP J.
• Granted Patent: US 8,880,944 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/3404 for parallel or distributed programming
• CPC Class Codes: G06F 2201/86 Event-based monitoring

Abstract

Restarting event and alert analysis after a shutdown in a distributed processing system includes identifying a shutdown condition of the distributed processing system; determining whether the shutdown was a planned shutdown or an unplanned shutdown; if the shutdown was planned, storing an identification of the last event in an event log that was injected in an event queue at the time of the planned shutdown and restarting event and alert analysis using the next event identified in the event log; and if the shutdown was unplanned, for each event analyzer, identifying the last event included in the last event pool that the event analyzer closed; and restarting event and alert analysis at the event analyzer using the next event received by the event analyzer after the identified last event.

Claims

1. A method of restarting event and alert analysis after a shutdown in a distributed processing system, the method comprising:

identifying, by an incident analyzer, a shutdown condition of the distributed processing system, the incident analyzer including a plurality of event analyzers and a monitor that monitors the plurality of event analyzers; and

determining, by the incident analyzer, whether the shutdown was a planned shutdown or an unplanned shutdown;

if the shutdown was planned, storing, by the incident analyzer, an identification of the last event in an event log that was injected in an event queue at the time of the planned shutdown and restarting, by the incident analyzer, event and alert analysis using the next event identified in the event log; and

if the shutdown was unplanned, for each event analyzer, identifying the last event included in the last event pool that the event analyzer closed; and

restarting, by the incident analyzer, event and alert analysis at the event analyzer using the next event received by the event analyzer after the identified last event.

2. The method of claim 1, wherein identifying the last event included in the last event pool that the event analyzer closed includes:

assigning, by each event analyzer, a checkpoint to each last event included in the event pool that is closed by the event analyzer; and

determining, by the monitor, for each event analyzer, the last checkpoint assigned.

3. The method of claim 2, wherein restarting event and alert analysis at the event analyzer using the next event received after by the event analyzer after the identified last event includes identifying, by the incident analyzer, the next event in dependence upon the last assigned checkpoint.

4. The method of claim 1, wherein restarting event and alert analysis at the event analyzer using the next event after the identified last event includes:

identifying, by the incident analyzer, all events that were not included in the last pool that is closed by the event analyzer; and

including, by the incident analyzer, the identified events in a next pool.

5. The method of claim 4, wherein identifying all events that were not included in the last pool that is closed by the event analyzer includes receiving from each event analyzer, by the monitor, a list of events that were moved forward.

6. The method of claim 4, wherein restarting event and alert analysis at the event analyzer using the next event after the identified last event includes:

identifying, by the incident analyzer, any events in the identified events that have already been processed; and

ignoring, by the incident analyzer, the identified already processed events.

7-18. -18. (canceled)