IP Library Granted Patent US 7,058,957
Granted Patent B1
US 7,058,957 · App. 10/194,710 · Granted Jun 6, 2006

Cluster event notification system

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,058,957
App. No.
10/194,710
Granted
Jun 6, 2006
Kind
B1
Abstract

A method for notifying events to a node in a cluster includes (1) receiving a first event message and a second event message, (2) queuing the first and the second event messages, (3) sending the first event message to a first service callback, wherein the first service callback calls a first callback function to handle the first event message, (4) sending the first event message to a second service callback after (a) a the first service callback has handled the first event message and (b) a corresponding first service callback at a member node has handled the first event message, wherein the second service callback calls a second callback function to handle the first event message, and (5) sending the second event message to the first service callback after the first and the second callback functions have handled the first event message, wherein the first service callback calls the first callback function to handle the second event message. The method may further include sending a dummy message to the first callback function if the first callback function is waiting for a message from a sending node that is down. The method may also include sending a node down message to the first callback function if the first callback function is sending a message to a receiving node that is down.

Claims (18)

1. A computer implemented method for notifying events in a node of a cluster, comprising:

receiving a first and a second event messages;

queuing the first and the second event messages;

sending the first event message to a first service callback, wherein the first service callback calls a first callback function to handle the first event message;

sending the first event message to a second service callback after (1) the first service callback has handled the first event message and (2) a corresponding first service callback at another node has handled the first event message, wherein the second service callback calls a second callback function to handle the first event message; and

sending the second event message to the first service callback after the first and the second service callbacks have handled the first event message, wherein the first service callback calls the first callback function to handle the second event message.

2. The computer implemented method of claim 1 , further comprising:

sending a dummy message to the first callback function if the first callback function is waiting for a message from a sending node that is down.

3. The computer implemented method of claim 1 , further comprising:

determining if the first callback function is waiting for a message from a sending node;

if the first callback function is waiting for a message, determining if there is an event message in queue indicating the sending node is down; and

if there is an event message in queue indicating the sending node is down, sending a dummy message on behalf of sending node to the first callback function.

4. The computer implemented method of claim 1 , further comprising:

sending a node down message to the first callback function if the first callback function is sending a message to a receiving node that is down.

5. The computer implemented method of claim 1 , further comprising:

determining if the first callback function is sending a message to a receiving node;

if the first callback function is sending a message to a receiving node, determining if there is an event message in queue indicating the receiving node is down; and

if there is an event message in queue indicating the receiving node is down, sending a node down message to the first callback function.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 9, 2015
From: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 037079/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 10, 2011
From: 3PAR INC.
To: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
Reel/Frame 026250/0322 →
CHANGE OF NAME Recorded Feb 28, 2008
From: 3PARDATA, INC.
To: 3PAR INC.
Reel/Frame 020571/0664 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 4, 2003
From: NGUYEN, VY
To: 3PARDATA, INC.
Reel/Frame 013802/0388 →