Cluster membership monitor

• US 20030041138A1
• Filed: 05/22/2002
• Published: 02/27/2003
• Est. Priority Date: 05/02/2000
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Mckinty, Stephen, Colas, Isabelle, Blanc, Florence, Vigouroux, Xavier-Francois, Kampe, Mark, Penkler, David, Ramer, Rebecca A.
• Application Number:
  US10/152,342
• Publication Number:
  US 20030041138A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0663 Performing the actions predefined by failover planning, e.g. switching to standby network elements
• CPC Class Codes: H04L 41/085 Retrieval of network configuration; Tracking network configuration history
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/12 Network monitoring probes
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1044 Group management mechanisms management of multicast group membership H04L12/185; reconfiguring of node membership in a computing system to eliminate errors G06F11/1425
• CPC Class Codes: H04L 67/1046 Joining mechanisms
• CPC Class Codes: H04L 67/1048 Departure or maintenance mechanisms

Abstract

The present invention describes a computer network including a network membership manager. In particular, a group of nodes on a computer network are managed by a distributed membership manager. Nodes of the computer network contain membership managers that manage the interaction between the nodes. Management of the computer network includes propagating configuration data to the nodes, providing an election process for determining the master node within a group of nodes, and monitoring the health of each node so that a change in the configuration and/or management structure can be accommodated by the nodes of the network.

Claims

1. A computer network comprising:

a plurality of nodes;

a communications channel connecting the plurality of nodes allowing each node to communicate one with another;

a first membership monitor associated with a first node for receiving from, storing, and broadcasting to the network information used in the management of the plurality of nodes; and

a second membership monitor associated with a second node for receiving from, storing, and broadcasting to the network information used in the management of the plurality of nodes.

2. The computer network of claim 1, wherein the communications channel includes redundant connections to each node of the plurality of nodes.

3. The computer network of claim 1, wherein the communications channel includes a first domain address associated with the plurality of nodes.

4. The computer network of claim 1, wherein the communications channel includes a node address for each node.

5. The computer network of claim 1, further comprising a second plurality of nodes.

6. The computer network of claim 5, wherein the communications channel includes a second domain address for the second plurality of nodes.

7. The computer network of claim 1, wherein the first membership monitor is a master node.

8. The computer network of claim 1, wherein the second membership monitor is a vice-master node.

9. The computer network of claim 1, wherein the second membership monitor is a peer node.

10. The computer network of claim 1, further comprising an LDAP data store accessible by the first membership monitor.

11. The computer network of claim 1, further comprising a non-volatile random access memory accessible by the first membership monitor.

12. The computer network of claim 1, further comprising a flat data file accessible by the first membership monitor.

13. The computer network of claim 1, wherein the first membership monitor is interconnected with a local data store.

14. The computer network of claim 1, wherein the second membership monitor is interconnected with a local data store.

15. A membership monitor associated with a node of a computer network comprising:

a data store for storing current configuration data;

a management element for receiving from, storing, and broadcasting to the network information used in the management of the node; and

a programming interface interconnected with the management element providing an interface to an application, and services.

16. The membership monitor of claim 15, wherein the management element further comprises a core module for managing, synchronizing, and starting the membership monitor.

17. The membership monitor of claim 15, wherein the management element further comprises a configuration module for managing the initiation, modification, and propagation of configuration data.

18. The membership monitor of claim 17, wherein the configuration module is interconnected with a lightweight directory access protocol data store.

19. The membership monitor of claim 18, wherein the configuration module includes a data management component for managing interactions with the lightweight directory access protocol data store.

20. The membership monitor of claim 17, wherein the configuration module is connected to a flat file data store.

21. The membership monitor of claim 17, wherein the configuration module is connected to a non-volatile random access memory.

22. The membership monitor of claim 15, wherein the management element further comprises an election module for processing the election of a master membership monitor among a group of nodes.

23. The membership monitor of claim 15, further comprising a communications interface interconnected with the management element providing an interface to the computer network.

24. The membership monitor of claim 15, further comprising a probe for monitoring the health of the node.

25. A method for managing a group of nodes on a computer network by a membership monitor comprising the steps of:

maintaining a data store of configuration data; and

propagating the configuration data from a first membership monitor on a first node in the group of nodes to a second membership monitor on a second node in the group of nodes.

26. The method of claim 25, wherein the step of maintaining a data store of configuration data comprises the step of maintaining a data store of configuration data on a lightweight directory access protocol data store.

27. The method of claim 25, wherein the step of maintaining a data store of configuration data comprises the steps of:

maintaining a domain id;

maintaining a nodes table; and

maintaining a subnet mask.

28. The method of claim 27, wherein the step of maintaining a nodes table comprises the steps of:

maintaining a node id for each node of the group of nodes;

maintaining a node name for each node of the group of nodes; and

maintaining a list of administrative attributes for each node of the group of nodes.

29. The method of claim 25, further comprising the step of notifying the first membership monitor of a change in the configuration data.

30. The method of claim 29, wherein the step of notifying the first membership monitor of a change in the configuration data comprises the step of notifying the first membership monitor each time there is a change in the configuration data.

31. The method of claim 29, wherein the step of notifying a first membership monitor of a change in the configuration data comprises the step of notifying the first membership monitor when the number of changes in the configuration data reaches a predetermined limit.

32. The method of claim 25, wherein the step of propagating the configuration data from a first membership monitor on a node in the group of nodes to a second membership monitor on a node in the group of nodes comprises the step of sending an information package by the first membership monitor to the second membership monitor.

33. The method of claim 32, wherein the step of sending an information package by the first membership monitor to the second membership monitor comprises the step of sending a single configuration change to the second membership monitor.

34. The method of claim 32, wherein the step of sending an information package by the first membership monitor to the second membership monitor comprises the step of sending a list of changes to the second membership monitor.

35. The method of claim 32, wherein the step of sending an information package by the first membership monitor to the second membership monitor comprises the step of sending the entire contents of the data store of configuration data to the second membership monitor.

36. The method of claim 25, wherein the step of propagating the configuration data from a first membership monitor on a first node in the group of nodes to a second membership monitor on a second node in the group of nodes further comprises the step of requesting by the second membership monitor a transmission of the configuration data.

37. The method of claim 25, wherein the step of propagating the configuration data from a first membership monitor on a first node in the group of nodes to a second membership monitor on a second node in the group of nodes further comprises sending by the first membership monitor a revision number to the second membership monitor.

38. The method of claim 37, further comprising the step of updating a local copy of configuration data by the second membership monitor if the revision number is greater than a previously received revision number.

39. The method of claim 25, further comprising the step of sending membership data by the first membership monitor to the second membership monitor.

40. The method of claim 25, further comprising the step of notifying an application programming interface of the first membership monitor of a change in the configuration data.

41. The method of claim 25, further comprising the step of notifying an application programming interface of the second membership monitor of a change in the configuration data.