Failover management system

• US 20030005350A1
• Filed: 06/29/2001
• Published: 01/02/2003
• Est. Priority Date: 06/29/2001
• Status: Abandoned Application

• Current Assignee: Wind River Systems Incorporated (Aptiv PLC)
• Original Assignee: Wind River Systems Incorporated (Aptiv PLC)
• Inventors: Zhang, Yiming, Johnson, Tod, Koning, Maarten
• Application Number:
  US09/896,959
• Publication Number:
  US 20030005350A1
• Time in Patent Office: Days
• US Class Current: 714/4
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A system is provided which includes a plurality of nodes, wherein each node has a processor executable thereon. The system also includes a first failover server group that includes a first server that is capable of performing a first service and a second server capable of performing the first service. The first server is executable on a first node of the plurality of nodes and the second server is executable on a second node of the plurality of nodes. The third server is executable on the first node and the fourth server being executable on one of the plurality of nodes other than the first node. The system also includes a second failover server group that includes a third server capable of performing a second service and a fourth server capable of performing the second service. The first, second, third and fourth servers can each be in one of a plurality of states including an active state and a standby state. The system also includes a failover management system that, upon determining that a failure has occurred on the first node, instructs the second server to change its state to the active state if the first server was in the active state when the failure determination occurred, and instructs the fourth server to change its state to the active state if the third server was in the active state when the failure determination occurred.

Claims

1. A system comprising:

a plurality of nodes, each node having a processor executable thereon;

a first server group, the first server group including a first server capable of performing a first service and a second server capable of performing the first service, the first server being in one of a plurality of states including an active state and a standby state, the second server being in one of the active state and an inactive state, the first server being executable on a first node of the plurality of nodes and the second server being executable on a second node of the plurality of nodes;

a second server group, the second server group including a third server capable of performing a second service and a fourth server capable of performing the second service, the third server being in one of the plurality of states including the active state and the standby state, the fourth server being in one of the active state and an inactive state, the third server being executable on the first node, the fourth server being executable on one of the plurality of nodes other than the first node;

a failover management system, the failover management system, upon determining that a failure has occurred on the first node, instructing the second server to change its state to the active state if the first server was in the active state when the failure determination occurred, and instructing the fourth server to change its state to the active state if the third server was in the active state when the failure determination occurred.

2. The system of claim 1, wherein the failover management system includes a failover management process executing on each of the first node, the second node, and one of the plurality of nodes other than the first node.

3. The system of claim 2, wherein the failover management process on the first node includes information indicative of a current one of the plurality of states for the first server, the second server, the third server, and the fourth server.

4. The system of claim 3, wherein the failover management process on the first node is operable to notify the failover processes on the second node and on the one of the plurality of nodes other than the first node of the current state of the first server and the third server.

5. The system of claim 1, wherein the plurality of states include the active state, the standby state, an initializing state, a failed state, and an offline state.

6. The system of claim 5, wherein the plurality of states include an unknown state.

7. The system of claim 1, further comprising a fifth server on one of the plurality of nodes, the fifth server not forming a part of any failover server group, the fifth server being operable to request the first service from the first server, and wherein the failover management system notifies the fifth server of changes in the state of the first server.

8. The system of claim 7, wherein the fifth server is notified of changes in the state of the first server via a monitor executing on the one of the plurality of nodes.

9. The system of claim 1, further comprising a heartbeat management system on each of the first node, second node, and the one of the plurality of nodes other than the first node, each heartbeat management system periodically transmitting a message to a common one of the plurality of nodes.

10. The system of claim 9, wherein the heartbeat message includes a current state of the node on which the heartbeat management system transmitting the heartbeat message resides.

11. The system of claim 10, wherein the common one of the plurality of nodes has a global failover controller executing thereon.

12. The system of claim 11, wherein the common one of the plurality of nodes is one of the first node, the second node, and the one of the plurality of nodes other than the first node.

13. The system of claim 10, wherein the common one of the plurality of nodes is a third node, and wherein the third node has a global failover controller executing thereon, and the first node, the second node, and the one of the plurality of nodes other than the first node each have a respective local failover controller executing thereon.

14. The system of claim 1, further comprising a heartbeat management system on each of the first node, second node, and the one of the plurality of nodes other than the first node, each heartbeat management system, in response to a heartbeat message received from a heartbeat management system on another node in the system, transmits a heartbeat message to said node in the system.

15. The system of claim 14, wherein the heartbeat message includes a current state of the node on which the heartbeat management system transmitting the message resides.

16. The system of claim 1, further comprising a monitor on at least one of the nodes, the monitor having associated therewith a software entity and a target, the target being one of the first server, the second server, the third server, the fourth server, the first server group, and the second server group, and wherein the monitor notifies the software entity of status changes in the target.

18. The failover management process of claim 17, wherein the step of monitoring the third server comprises receiving a heartbeat message, the heartbeat message including information indicative of the status of the third server.

19. The failover management process of claim 18, wherein the step of monitoring the fourth server comprises receiving a heartbeat message, the heartbeat message including information indicative of the current state of the fourth server.

20. The failover management process of claim 19, wherein the heart beat messages is transmitted by a global failover controller, and wherein the global failover controller receives information indicative of the current state of the fourth server from the remote node executing the fourth server and wherein the global failover controller receives information indicative of the current state of the third server from the remote node executing the third server.

21. The failover management process of claim 20, wherein the notifying step further comprises transmitting state changes to the first and second servers to the global failover controller, and wherein the global failover controller notifies the process on the remote node executing the third server and the process on the remote node executing the fourth server of changes in the current state of the first server and the second server

26. The failover management process of claim 17, wherein the remote node executing the third server is a first node.

29. The system of claim 1, wherein the inactive state is one of the standby state, a failed state, and an offline state.

30. The system of claim 2, wherein the first node can be in one of a plurality states including the active state and an inactive state, the second node can be in one of a plurality states including the active state and an inactive state, and the node other than the first node can be in one of a plurality states including the active state and an inactive state.

31. The system of claim 31, wherein the failover management process on the first node includes information indicative of a current one of the plurality of states for the first server, the second server, the third server, the fourth server, the first node, the second node, and the node other than the first node.

32. The system of claim 31 wherein the failover management process on the first node is operable to notify the failover processes on the second node and on the one of the plurality of nodes other than the first node of the current state of the first server, the third server, and the first node.

33. The system of claim 1, further comprising an application on one of the plurality of nodes, the application being operable to request the first service from the first server, and wherein the failover management system notifies the application of changes in the state of the first server.

34. The system of claim 1, further comprising a monitor on at least one of the nodes, the monitor having associated therewith a software entity and a target, the target being one of the first server, the second server, the third server, the fourth server, the first server group, and the second server group, the first node, the second node, and the node other than the first node, and wherein the monitor notifies the software entity of status changes in the target.

36. The computer readable medium of claim 35, wherein the step of monitoring the third server comprises receiving a heartbeat message, the heartbeat message including information indicative of the status of the third server.

37. The computer readable medium of claim 36, wherein the step of monitoring the fourth server comprises receiving a heartbeat message, the heartbeat message including information indicative of the current state of the fourth server.

38. The computer readable medium of claim 37, wherein the heart beat messages is transmitted by a global failover controller, and wherein the global failover controller receives information indicative of the current state of the fourth server from the remote node executing the fourth server and wherein the global failover controller receives information indicative of the current state of the third server from the remote node executing the third server.

39. The computer readable medium of claim 38, wherein the notifying step further comprises transmitting state changes to the first and second servers to the global failover controller, and wherein the global failover controller notifies the process on the remote node executing the third server and the process on the remote node executing the fourth server of changes in the current state of the first server and the second server.

17. A failover management process executable on a node that includes a first server in a first server group and a second server in a second server group, the failover management process comprising the steps of:

determining a current state of the first server and a current state of the second server, the current state of each server being one of a plurality of states including an active state, a standby state, and a failed state;

monitoring a current state of a third server on a remote node, the third server being one of the servers in the first server group, the current state of the third server being one of the plurality of states including the active state, the standby state, and the failed state;

monitoring a current state of a fourth server on a remote node, the fourth server being one of the servers in the second server group, the current state of the fourth server being one of the plurality of states including the active state, the standby state, and the failed state;

notifying a process on the remote node executing the third server and a process on the remote node executing the fourth server of changes in the current state of the first server and the second server;

if the current status of the first server is the standby state, and the current state of the third server is the failed state, changing the current state of the first server to the active state;

if the current state of the second server is the standby state, and the current state of the fourth server is the failed state, changing the current state of the second server to the active state.

22. A system comprising:

a plurality of nodes, each node having a processor executable thereon;

a first server group, the first server group including a first server capable of performing a first service and a second server capable of performing the first service, the first server being in one of a plurality of states including an active state and a standby state, the second server being in one of the active state and an inactive state, the first server being executable on a first node of the plurality of nodes and the second server being executable on a second node of the plurality of nodes;

a second server group, the second server group including a third server capable of performing a second service and a fourth server capable of performing the second service, the third server being in one of the plurality of states including the active state and the standby state, the fourth server being in one of the active state and an inactive state, the third server being executable on the first node, the fourth server being executable on a third node of the plurality of nodes;

a failover management system, the failover management system, upon determining that a failure has occurred on the first server but not on the third server, instructing the second server to change its state to the active state if the first server was in the active state when the failure determination occurred, the fourth server remaining in a standby state if the third server was in the active state when the failure determination occurred.

24. The system of claim 23, wherein the node other than the second node and the third node of the plurality of nodes is a fourth node, and wherein the fourth node has a third local failover controller executable thereon, the third local failover controller notifying the global failover controller of a current state of the fourth server.

25. The system of claim 23, wherein the node other than the second node and the third node of the plurality of nodes is the first node.

27. The failover management process of claim 26, wherein the remote node executing the fourth server is a second node.

28. The failover management process of claim 26, wherein the remote node executing the fourth server is the first node.

23. A failover management system, comprising:

a global failover controller executable on a first node of a plurality of nodes;

a first server group, the first server group including a first server capable of performing a first service and a second server capable of performing the first service, the first server being in one of a plurality of states including an active state and a standby state, the second server being in one of the active state and an inactive state, the first server being executable on a second node of the plurality of nodes and the second server being executable on a third node of the plurality of nodes;

a second server group, the second server group including a third server capable of performing a second service and a fourth server capable of performing the second service, the third server being in one of the plurality of states including the active state and the standby state, the fourth server being in one of the active state and an inactive state, the third server being executable on the first node, the fourth server being executable on a node other than the second node and the third node of the plurality of nodes;

a first local failover controller executable on the second node, and a second local failover controller executable on the third node, the first local failover controller notifying the global failover controller of a current state of the first server and the third server, the second local failover controller notifying the global failover controller of a current state of the second server;

the global failover controller notifying the first local failover controller of the current state of the second server and the fourth server and notifying the second failover controller of a current state of the first server;

the first local failover controller, upon receiving notification that the second server is in an inactive state, instructing the first server to change its state to the active state if the first server was in an inactive state when the notification was received,

the second local failover controller, upon receiving notification that the first server is in an inactive state, instructing the second server to change its state to the active state if the second server was in an inactive state when the notification was received,

the first local failover controller, upon receiving notification that the fourth server is in an inactive state, instructing the third server to change its state to the active state if the fourth server was in an inactive state when the notification was received.

35. A computer readable medium, having stored thereon, computer executable process steps that are executable on a node that includes a first server in a first server group and a second server in a second server group, the computer executable process steps comprising:

determining a current state of the first server and a current state of the second server, the current state of each server being one of a plurality of states including an active state, a standby state, and a failed state;

monitoring a current state of a third server on a remote node, the third server being one of the servers in the first server group, the current state of the third server being one of the plurality of states including the active state, the standby state, and the failed state;

monitoring a current state of a fourth server on a remote node, the fourth server being one of the servers in the second server group, the current state of the fourth server being one of the plurality of states including the active state, the standby state, and the failed state;

notifying a process on the remote node executing the third server and a process on the remote node executing the fourth server of changes in the current state of the first server and the second server;

if the current status of the first server is the standby state, and the current state of the third server is the failed state, changing the current state of the first server to the active state;

if the current state of the second server is the standby state, and the current state of the fourth server is the failed state, changing the current state of the second server to the active state.

40. A system comprising:

a plurality of nodes, each node having a processor executable thereon;

a first server group, the first server group including a first server capable of performing a first service and a second server capable of performing the first service, the first server being in one of a plurality of states including an active state, a standby state, an offline state, an initialized state and a failed state, the second server being in one of the active state, the standby state, the offline state, the initialized state, and the failed state, the first server being executable on a first node of the plurality of nodes and the second server being executable on a second node of the plurality of nodes;

a second server group, the second server group including a third server capable of performing a second service and a fourth server capable of performing the second service, the third server being in one of the plurality of states including the active state, the standby state, the offline state, the initialized state and the failed state, the fourth server being in one of the active state and the standby state, the failed state, the initialized state and the offline state, the third server being executable on the first node, the fourth server being executable on one of the plurality of nodes other than the first node;

a failover management system, the failover management system, upon determining that a failure has occurred on the first node, instructing the second server to change its state to the active state if the first server was in the active state when the failure determination occurred and if the second server was not in one of the failed state, the initialized state, and the offline state, and instructing the fourth server to change its state to the active state if the third server was in the active state when the failure determination occurred, and if the fourth server was not in one of the failed state, the initialized state, and the offline state