WO2009121689A1 - Method for enabling faster recovery of client applications in the event of server failure - Google Patents

Method for enabling faster recovery of client applications in the event of server failure Download PDF

Info

Publication number
WO2009121689A1
WO2009121689A1 PCT/EP2009/052803 EP2009052803W WO2009121689A1 WO 2009121689 A1 WO2009121689 A1 WO 2009121689A1 EP 2009052803 W EP2009052803 W EP 2009052803W WO 2009121689 A1 WO2009121689 A1 WO 2009121689A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
client
server
fallover
notification
Prior art date
Application number
PCT/EP2009/052803
Other languages
French (fr)
Inventor
Michael Coffey
Manjunath Basappa Muttur
Original Assignee
International Business Machines Corporation
Ibm United Kingdom Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by International Business Machines Corporation, Ibm United Kingdom Limited filed Critical International Business Machines Corporation
Priority to CA2706579A priority Critical patent/CA2706579C/en
Priority to EP09729022.5A priority patent/EP2274898B1/en
Priority to BRPI0911284-7A priority patent/BRPI0911284B1/en
Priority to JP2011502320A priority patent/JP5695558B2/en
Priority to CN200980120431.9A priority patent/CN102047643B/en
Priority to KR1020107024139A priority patent/KR101419579B1/en
Publication of WO2009121689A1 publication Critical patent/WO2009121689A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2023—Failover techniques
    • G06F11/2028—Failover techniques eliminating a faulty processor or activating a spare
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/163—In-band adaptation of TCP data exchange; In-band control procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2023—Failover techniques
    • G06F11/203—Failover techniques using migration

Definitions

  • the present invention is generally directed to multinode data processing systems and methods. More particularly, the present invention is directed to a system and method for improving recovery time in the event of a server failure. Even more particularly, the present invention is directed to a system in which a fallover node provides failure notification as opposed to waiting for a determination of failure based on the lack of performance by the failed node.
  • a fallover node provides failure notification as opposed to waiting for a determination of failure based on the lack of performance by the failed node.
  • clusterware applications such as HACMP (High Availability Cluster Management Program)
  • client applications which are intelligent enough to automatically reconnect to a backup server when the primary server fails. This is made possible by dynamically moving the IP (Internet Protocol) address of the primary server, with which a client was interacting, to the backup server. Accordingly, client applications do not have to be killed and/or restarted in response to a server failure.
  • This capability of clusterware is referred to herein as "fallover.”
  • the problem is that, as soon as the primary server fails, the TCP (Transmission Control Protocol) connection existing between the client and the server takes some time to get terminated. This is primarily because client applications are unaware of the server failure and so the client application keeps retransmitting until the
  • the delay described above is avoided by timely notification of the failure event to the client.
  • the client preferably reconnects as soon as it receives this notification about the server failure.
  • the present invention preferably provides a mechanism for speeding up the process of reconnection, to one or more backup servers within cluster, by a client application.
  • the client preferably receives a RST (Reset Packet) for that TCP connection as soon as the server fails.
  • RST Set Packet
  • the method of the present invention still preferably generates this RST packet.
  • the fallover node backup server
  • the fallover node preferably sends this RST packet to the client. In effect the fallover node pretends to be the failed node for the client.
  • a method for improving recovery in fallover conditions comprises the step of sending notification of the failure of a server node, which is acting as server for a client application running on a client node, to the client application. This notification is provided by the fallover node acting as backup for the server node.
  • the fallover node masquerades as the server node in order to send the notification of failure.
  • a data packet is received from the client application. This packet is accessed to determine transmission information and the transmission information is used to send notification of failure of the server node to the client application.
  • the data packet is one that has been retransmitted by the client application when no acknowledgement of the original transmission of the data packet to the server node was received by the client application.
  • the fallover node informs said client node that the fallover node has taken over for said server node. Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention.
  • FIG. 1 is a block diagram illustrating the connections between a basic node configuration environment in which the present invention is employed and also illustrates a sequence of events that occurs in the operation of a preferred embodiment of the present invention
  • FIG. 2 is a flow chart illustrating a sequence of events that typically occurs in the process of a preferred embodiment of the present invention.
  • a client may be communicating with a server using, for example, the TCP protocol. If the server fails, the client may not notice that this has happened. In the absence of any acknowledgements to the packets the client sends out, the client will keep retransmitting until the TCP retransmit counter expires. This could be quite some time later. It is desirable therefore to force the connection between the client and the server to be terminated and reset.
  • the TCP protocol has a RESET (RST) option.
  • RST RESET
  • the invention in accordance with a preferred embodiment, makes use of a backup (or fallover) server which monitors a server node with which the client is communicating.
  • the fallover node When the fallover node notices that the server node has failed, the fallover node takes over the address of the server node. At this point the backup server looks at all traffic on the taken over IP address to see if any is destined for (i.e. addressed to) the application that used to run on the server node, but has been restarted on the backup node along with the IP address. If it finds any it then 'masquerades" as the server node.
  • the fallover node however has no knowledge of the connections that were held by the server node.
  • the fallover node doesn't know who held them or what type of connections they held.
  • the fallover node therefore needs to be able to deduce who the server node had a connection with and to then 'encourage' (using the RST option) such clients to connect to the fallover node. Naturally this would be transparent to any such clients who would think they were reconnecting to the server node.
  • the client has to believe that the RST packet came from the server node.
  • every packet has a sequence number and "ACK" number which insures that data is properly ordered at the end of the transmission at the receiver.
  • ACK acknowledges that data is properly ordered at the end of the transmission at the receiver.
  • application "A” has to determine the sequence number, ACK number, and TCP header information for the next packet in the TCP sequence to be sent to the client.
  • the backup server (fallover node) to be able to send a RST (Reset) packet to the client it has to determine appropriate TCP header information for that RST packet.
  • RST reset
  • the fallover node has taken over the address of the server. The fallover node therefore receives some retransmitted packets from the client as soon as it acquires (by activating) the IP address from the failed node.
  • the backup server (fallover node) obtains TCP header information of the next packet in the sequence using the retransmitted packet it just received from the client. This TCP header information enables the backup server to determine for example what sequence number the RST packet should use and where the RST packet should be sent.
  • any application can handcraft a packet and send it on a TCP connection existing between two different applications.
  • This newly crafted packet appears to be a genuine packet for the receiver since it thinks that it is sent by its peer application.
  • clusterware such as HACMP handcrafts a RST packet using raw IP sockets and send it to the client.
  • This RST packet breaks the old TCP connection immediately and hence a client can reconnect again quickly.
  • Figure 1 illustrates, in accordance with a preferred embodiment, a sequence of events or situations in the use of the present invention.
  • the "1" in the circle indicates an initial state in which client node 100 is in communication with server node 200.
  • the “2” in the circle indicates the event in which server node 200 fails and there is a fallover to fallover node 300.
  • the “3” in the circle indicates the event in which fallover node 300 communicates to client node 100 that server node 200 has failed and that it is taking over the communication function.
  • the "4" in the circle indicates a final status in which client node 100 is now connected to fallover node 300.
  • the illustrated process avoids the necessity of an application running on client node 100 having to wait for an indication of failure for node 200 which is long in coming since application level software is not typically aware of node failures.
  • the fallover process, running at system level speeds and priorities occurs much faster and this fact along with the protocol structure of TCP connections allows a much faster notification to a client based server application.
  • Figure 2 illustrates a typical sequence of events that occurs in the process of the present invention.
  • the process is triggered by the failure of server node 200 (step 101).
  • System level software detects this failure in a relatively rapid fashion and provides a fallover to fallover (or backup) node 300 (step 102).
  • Fallover node 300 then provides notification to client node 100 (step 103).
  • Client node 100 then terminates the connection to node 200 (step 104).
  • the present invention also encompasses software in the form of machine readable instructions for carrying out the process recited herein. Furthermore, the present invention encompasses data processing systems having such instructions disposed within the memories thereof for carrying out the recited process.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)

Abstract

A system and method are provided for improving recovery times in fallover conditions in a multinode data processing system by sending notification of the failure of a server node, which is acting as server for a client application running on a client node, to the client application. In the present invention, this notification is provided by the fallover node acting as backup for the server node. When a client application receives no response from a server for a long time, it assumes that the server has failed and initiates reconnection. The present invention speeds-up the reconnect initiated by the client application by having system level software proactively notify the client application about the server failure. This results in faster recovery for client applications.

Description

METHOD FOR ENABLING FASTER RECOVERY OF CLIENT APPLICATIONS
IN THE EVENT OF SERVER FAILURE
Technical Field
The present invention is generally directed to multinode data processing systems and methods. More particularly, the present invention is directed to a system and method for improving recovery time in the event of a server failure. Even more particularly, the present invention is directed to a system in which a fallover node provides failure notification as opposed to waiting for a determination of failure based on the lack of performance by the failed node. As used herein and in the appended claims, the terms "node" and "server" are used interchangeably, though it is understood that a server may include several nodes.
Background of the Invention
In clusterware applications such as HACMP (High Availability Cluster Management Program), there exists many client applications which are intelligent enough to automatically reconnect to a backup server when the primary server fails. This is made possible by dynamically moving the IP (Internet Protocol) address of the primary server, with which a client was interacting, to the backup server. Accordingly, client applications do not have to be killed and/or restarted in response to a server failure. This capability of clusterware is referred to herein as "fallover." However, the problem is that, as soon as the primary server fails, the TCP (Transmission Control Protocol) connection existing between the client and the server takes some time to get terminated. This is primarily because client applications are unaware of the server failure and so the client application keeps retransmitting until the
TCP retransmit counter expires, thus eventually terminating the TCP connection. Accordingly, it is seen that it takes a considerable amount of time for client applications to recognize the server failure event before attempting a reconnect to backup server. From the above, it is therefore seen that there exists a need in the art to overcome the deficiencies and limitations described herein and above. Summary of the Invention
The delay described above is avoided by timely notification of the failure event to the client. The client preferably reconnects as soon as it receives this notification about the server failure. The present invention preferably provides a mechanism for speeding up the process of reconnection, to one or more backup servers within cluster, by a client application. To quickly terminate all of the TCP connections existing between the server (the presumably failed node) and the client, the client preferably receives a RST (Reset Packet) for that TCP connection as soon as the server fails. Despite the failure of the node from which this RST packet is expected, the method of the present invention still preferably generates this RST packet. To achieve this, as soon as the fallover happens, the fallover node (backup server) preferably sends this RST packet to the client. In effect the fallover node pretends to be the failed node for the client.
In accordance with one embodiment of the present invention, a method for improving recovery in fallover conditions comprises the step of sending notification of the failure of a server node, which is acting as server for a client application running on a client node, to the client application. This notification is provided by the fallover node acting as backup for the server node.
Preferably the fallover node masquerades as the server node in order to send the notification of failure. In accordance with a preferred embodiment, a data packet is received from the client application. This packet is accessed to determine transmission information and the transmission information is used to send notification of failure of the server node to the client application.
In accordance with a preferred embodiment, the data packet is one that has been retransmitted by the client application when no acknowledgement of the original transmission of the data packet to the server node was received by the client application. In one embodiment, the fallover node informs said client node that the fallover node has taken over for said server node. Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention.
The recitation herein of desirable objects which are met by various embodiments of the present invention is not meant to imply or suggest that any or all of these objects are present as essential features, either individually or collectively, in the most general embodiment of the present invention or in any of its more specific embodiments.
Brief Description of the Drawings
Preferred embodiments of the present invention will now be described, by way of example only, and with reference to the following drawings:
FIG. 1 is a block diagram illustrating the connections between a basic node configuration environment in which the present invention is employed and also illustrates a sequence of events that occurs in the operation of a preferred embodiment of the present invention; and
FIG. 2 is a flow chart illustrating a sequence of events that typically occurs in the process of a preferred embodiment of the present invention.
Detailed Description
As previously discussed, a client may be communicating with a server using, for example, the TCP protocol. If the server fails, the client may not notice that this has happened. In the absence of any acknowledgements to the packets the client sends out, the client will keep retransmitting until the TCP retransmit counter expires. This could be quite some time later. It is desirable therefore to force the connection between the client and the server to be terminated and reset. The TCP protocol has a RESET (RST) option. When two parties are communicating, if the first party notices that the other party has stopped communicating, then the first party may send an RST to force the other party to reset the connection. The point here is however that the client may not realize for quite some time that there is a problem. When the client does eventually realize that there is a problem, the client will then attempt to reconnect and will be connected to a fallover node.
The invention, in accordance with a preferred embodiment, makes use of a backup (or fallover) server which monitors a server node with which the client is communicating.
When the fallover node notices that the server node has failed, the fallover node takes over the address of the server node. At this point the backup server looks at all traffic on the taken over IP address to see if any is destined for (i.e. addressed to) the application that used to run on the server node, but has been restarted on the backup node along with the IP address. If it finds any it then 'masquerades" as the server node.
The fallover node however has no knowledge of the connections that were held by the server node. The fallover node doesn't know who held them or what type of connections they held. The fallover node therefore needs to be able to deduce who the server node had a connection with and to then 'encourage' (using the RST option) such clients to connect to the fallover node. Naturally this would be transparent to any such clients who would think they were reconnecting to the server node.
For this to work, the client has to believe that the RST packet came from the server node. In a TCP connection every packet has a sequence number and "ACK" number which insures that data is properly ordered at the end of the transmission at the receiver. At any point of time, if a TCP receives a packet with incorrect sequence number or ACK number, then it immediately discards that packet. So, for any application "A" to be able to send packets on a TCP connection existing between two other applications "B" and "C," application "A" has to determine the sequence number, ACK number, and TCP header information for the next packet in the TCP sequence to be sent to the client.
Similarly, for the backup server (fallover node) to be able to send a RST (Reset) packet to the client it has to determine appropriate TCP header information for that RST packet. In a TCP connection, when either of the communicating parties dies without terminating the connection by sending a FIN packet (which is used in TCP to indicate an end of transmission) or RST packet, the other party begins to retransmit the old packets again. In the preferred embodiment, the fallover node has taken over the address of the server. The fallover node therefore receives some retransmitted packets from the client as soon as it acquires (by activating) the IP address from the failed node. The backup server (fallover node) obtains TCP header information of the next packet in the sequence using the retransmitted packet it just received from the client. This TCP header information enables the backup server to determine for example what sequence number the RST packet should use and where the RST packet should be sent.
Using raw IP sockets, any application can handcraft a packet and send it on a TCP connection existing between two different applications. This newly crafted packet appears to be a genuine packet for the receiver since it thinks that it is sent by its peer application. In the present invention, clusterware such as HACMP handcrafts a RST packet using raw IP sockets and send it to the client. This RST packet breaks the old TCP connection immediately and hence a client can reconnect again quickly.
In this invention, there is no need to change either the existing client applications or the TCP stack itself. Irrespective of whether the TCP connection is terminated by TCP connection time-out or by RST packet, the client application views it as abrupt termination and attempts a reconnect.
Figure 1 illustrates, in accordance with a preferred embodiment, a sequence of events or situations in the use of the present invention. In particular, the "1" in the circle indicates an initial state in which client node 100 is in communication with server node 200. The "2" in the circle indicates the event in which server node 200 fails and there is a fallover to fallover node 300. The "3" in the circle indicates the event in which fallover node 300 communicates to client node 100 that server node 200 has failed and that it is taking over the communication function. The "4" in the circle indicates a final status in which client node 100 is now connected to fallover node 300. The illustrated process avoids the necessity of an application running on client node 100 having to wait for an indication of failure for node 200 which is long in coming since application level software is not typically aware of node failures. The fallover process, running at system level speeds and priorities occurs much faster and this fact along with the protocol structure of TCP connections allows a much faster notification to a client based server application.
Figure 2 illustrates a typical sequence of events that occurs in the process of the present invention. The process is triggered by the failure of server node 200 (step 101). System level software detects this failure in a relatively rapid fashion and provides a fallover to fallover (or backup) node 300 (step 102). Fallover node 300 then provides notification to client node 100 (step 103). Client node 100 then terminates the connection to node 200 (step 104).
The present invention also encompasses software in the form of machine readable instructions for carrying out the process recited herein. Furthermore, the present invention encompasses data processing systems having such instructions disposed within the memories thereof for carrying out the recited process.
While the invention has been described in detail herein in accordance with certain preferred embodiments thereof, many modifications and changes therein may be effected by those skilled in the art. Accordingly, it is intended by the appended claims to cover all such modifications and changes as fall within the spirit and scope of the invention.

Claims

1. A method for improving recovery in fallover conditions, said method comprising the step of: ending notification of failure of a server node, acting as server for a client application running on a client node, to said client application, said notification being provided by a fallover node acting as backup for said server node.
2. The method of claim 1 further including the step of terminating connection to said server node.
3. The method of claim 1 or 2 further including the step of activating at the fallover node the IP address originally associated with the server node.
4. The method of claim 3 further including the step receiving , at said fallover node, retransmitted packets at said client node.
5. The method of claim 4 further including the step of obtaining, at said fallover node, TCP header information.
6. The method of claim 5 in which said header information includes packet sequence number.
7. The method of claim 5 or 6 further including the step of constructing a Reset packet at said fallover node.
8. The method of claim 7 in which said Reset packet construction uses raw sockets.
9. The method of claim 7 or 8 further including the step of transmitting said Reset packet to said application running on said client node.
10. The method of claim 7, 8 or 9 further including the step of terminating connection from said client node to said server node.
11. The method of claim 10 further including the step of attempting reconnection by said application.
12. The method of any preceding claim in which said server node and said client note are in communication via Transmission Control Protocol.
13. The method of any preceding claim in which said fallover node informs said application running on said client node that said server node has failed.
14. The method of claim 13 in which said fallover node is operable to inform said client node that the fallover node has taken over for said server node.
15. The method of any preceding claim in which said method is triggered by failure of said server node.
16. The method of any preceding claim in which said notification is provided earlier than notification provided through a Transmission Control Protocol connection.
17. The method of any preceding claim, wherein the fallover node masquerades as the server node in order to send the notification of failure, the method comprising: receiving a data packet from the client application; and accessing the data packet to determine transmission information, wherein the step of sending notification of failure comprises: using the transmission information to send notification of failure of the server node to the client application.
18. The method of claim 17 wherein the data packet is one that has been retransmitted by the client application when no acknowledgement of the original transmission of the data packet to the server node was received by the client application.
19. A multinode data processing system including at least three nodes containing program instructions in memory for said nodes for sending notification of failure of a server node, which is acting as server for a client application running on a client node, to said client application, said notification being provided by a fallover node acting as backup for said server node.
20. The system of claim 19 further including means for terminating connection to said server node.
21. The system of claim 19 or 20 further including means for activating at the fallover node the IP address originally associated with the server node .
22. The system of claim 21 further including means for receiving, at said fallover node, retransmitted packets at said client node.
23. The system of claim 22 further including means for obtaining, at said fallover node, TCP header information.
24. The system of claim 23 in which said header information includes packet sequence number.
25. The system of claim 23 or 24 further including means for constructing a Reset packet at said fallover node.
26. The system of claim 25 in which said Reset packet construction uses raw sockets.
27. The system of claim 25 or 26 further including means for transmitting said Reset packet to said application running on said client node.
28. The system of claim 25, 26 or 27 further including means for terminating connection from said client node to said server node.
29. The system of claim 28 further including means for attempting reconnection by said application.
30. The system of any of claims 19 to 29 in which said server node and said client note are in communication via Transmission Control Protocol.
31. The system of any of claims 19 to 29 in which said fallover node informs said application running on said client node that said server node has failed.
32. The system of claim 31 in which said fallover node comprises means for informing said client node that the fallover node has taken over for said server node.
33. The system of any of claims 19 to 32 in which said method is triggered by failure of said server node.
34. The system of any of claims 19 to 33 in which said notification is provided earlier than notification provided through a Transmission Control Protocol connection.
35. The system of any of claims 19 to 34, wherein the fallover node masquerades as the server node in order to send the notification of failure, the system comprising: means for receiving a data packet from the client application; and means for accessing the data packet to determine transmission information, wherein the means for sending notification of failure comprises: means for using the transmission information to send notification of failure of the server node to the client application.
36. The system of claim 35, wherein the data packet is one that has been retransmitted by the client application when no acknowledgement of the original transmission of the data packet to the server node was received by the client application.
37. The system of any preceding claim in which said server node and said application running on said client node are initially connected through a Transmission Control Protocol connection.
38. A machine readable medium containing instructions thereon for sending notification of failure of a server node, which is acting as server for a client application running on a client node, to said client application, said notification being provided by a fallover node acting as backup for said server node.
39. The machine readable medium of claim 38 in which said server node and said application running on said client node are initially connected through a Transmission Control Protocol connection.
40. The machine readable medium of claim 38 or 39, wherein the fallover node masquerades as the server node in order to send the notification of failure, the machine readable medium comprising: instructions for receiving a data packet from the client application; and instructions for accessing the data packet to determine transmission information, wherein the instructions for sending notification of failure comprises: instructions for using the transmission information to send notification of failure of the server node to the client application.
41. The machine readable medium of claim 40, wherein the data packet is one that has been retransmitted by the client application when no acknowledgement of the original transmission of the data packet to the server node was received by the client application.
42. A computer program comprising program code means adapted to perform the method of any of claims 1 to 18 when said program is run on a computer.
PCT/EP2009/052803 2008-04-02 2009-03-10 Method for enabling faster recovery of client applications in the event of server failure WO2009121689A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CA2706579A CA2706579C (en) 2008-04-02 2009-03-10 Method for enabling faster recovery of client applications in the event of server failure
EP09729022.5A EP2274898B1 (en) 2008-04-02 2009-03-10 Method for enabling faster recovery of client applications in the event of server failure
BRPI0911284-7A BRPI0911284B1 (en) 2008-04-02 2009-03-10 method and apparatus to improve recovery in fallover conditions
JP2011502320A JP5695558B2 (en) 2008-04-02 2009-03-10 Method for enabling faster recovery of client applications in case of server failure
CN200980120431.9A CN102047643B (en) 2008-04-02 2009-03-10 Method for enabling faster recovery of client applications in the event of server failure
KR1020107024139A KR101419579B1 (en) 2008-04-02 2009-03-10 Method for enabling faster recovery of client applications in the event of server failure

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US12/061,185 2008-04-02
US12/061,185 US7971099B2 (en) 2008-04-02 2008-04-02 Method for enabling faster recovery of client applications in the event of server failure

Publications (1)

Publication Number Publication Date
WO2009121689A1 true WO2009121689A1 (en) 2009-10-08

Family

ID=40929637

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2009/052803 WO2009121689A1 (en) 2008-04-02 2009-03-10 Method for enabling faster recovery of client applications in the event of server failure

Country Status (8)

Country Link
US (1) US7971099B2 (en)
EP (1) EP2274898B1 (en)
JP (1) JP5695558B2 (en)
KR (1) KR101419579B1 (en)
CN (1) CN102047643B (en)
BR (1) BRPI0911284B1 (en)
CA (1) CA2706579C (en)
WO (1) WO2009121689A1 (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9450804B2 (en) 2009-09-03 2016-09-20 At&T Intellectual Property I, L.P. Anycast aware transport for content distribution networks
US8555105B2 (en) * 2010-04-12 2013-10-08 International Business Machines Corporation Fallover policy management in high availability systems
CN103685398B (en) * 2012-09-17 2015-08-19 腾讯科技（深圳）有限公司 Communication connection method for building up and communication system
US9591080B2 (en) 2012-09-17 2017-03-07 Tencent Technology (Shenzhen) Company Limited Method of establishing a network socket with a data server
CN104426703B (en) * 2013-09-11 2018-08-31 深圳市东方博雅科技有限公司 A kind of server updating method and system
US20150215158A1 (en) * 2014-01-28 2015-07-30 Qualcomm Incorporated Discriminating or prioritizing users during failover in a voip system
JP6575318B2 (en) * 2015-11-18 2019-09-18 富士通株式会社 Network control device, cluster system, and control program
CN105808391A (en) * 2016-04-05 2016-07-27 浪潮电子信息产业股份有限公司 Method and device for hot replacing CPU nodes
CN106357744A (en) * 2016-08-29 2017-01-25 浪潮(北京)电子信息产业有限公司 Cluster reconnection method and system for SMB (server message block) client and SMB client
CN113055373A (en) * 2017-03-30 2021-06-29 华为技术有限公司 Data transmission method and communication device
EP3884620A1 (en) * 2018-11-21 2021-09-29 Telefonaktiebolaget LM Ericsson (publ) Fast session restoration for latency sensitive middleboxes

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020087912A1 (en) 2000-12-29 2002-07-04 International Business Machines Corporation Highly available TCP systems with fail over connections
EP1231756A2 (en) * 2001-02-06 2002-08-14 Hewlett-Packard Company, A Delaware Corporation Method and system for maintaining connections in a network
US20050086342A1 (en) * 2003-09-19 2005-04-21 Andrew Burt Techniques for client-transparent TCP migration
US20070198710A1 (en) * 2004-12-30 2007-08-23 Xstor Systems, Inc. Scalable distributed storage and delivery
EP1892921A2 (en) 2000-10-26 2008-02-27 Intel Corporation Method and sytem for managing distributed content and related metadata

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0537903A2 (en) 1991-10-02 1993-04-21 International Business Machines Corporation Distributed control system
US5805785A (en) 1996-02-27 1998-09-08 International Business Machines Corporation Method for monitoring and recovery of subsystems in a distributed/clustered system
US6189111B1 (en) 1997-03-28 2001-02-13 Tandem Computers Incorporated Resource harvesting in scalable, fault tolerant, single system image clusters
US6023706A (en) 1997-07-11 2000-02-08 International Business Machines Corporation Parallel file system and method for multiple node file access
US5963963A (en) 1997-07-11 1999-10-05 International Business Machines Corporation Parallel file system and buffer management arbitration
US6223231B1 (en) * 1998-11-12 2001-04-24 Sun Microsystems, Inc. Method and apparatus for highly-available processing of I/O requests while application processing continues
US6523130B1 (en) 1999-03-11 2003-02-18 Microsoft Corporation Storage system having error detection and recovery
US6651242B1 (en) * 1999-12-14 2003-11-18 Novell, Inc. High performance computing system for distributed applications over a computer
US6675217B1 (en) 2000-07-06 2004-01-06 Microsoft Corporation Recovery of cluster consistency following failover
JP2003084996A (en) * 2001-09-11 2003-03-20 Hitachi Ltd Switching method for host computer
US7076555B1 (en) * 2002-01-23 2006-07-11 Novell, Inc. System and method for transparent takeover of TCP connections between servers
US7984157B2 (en) * 2002-02-26 2011-07-19 Citrix Systems, Inc. Persistent and reliable session securely traversing network components using an encapsulating protocol
JP3932994B2 (en) * 2002-06-25 2007-06-20 株式会社日立製作所 Server handover system and method
US7197660B1 (en) 2002-06-26 2007-03-27 Juniper Networks, Inc. High availability network security systems
US7152180B2 (en) * 2002-12-06 2006-12-19 Ntt Docomo, Inc. Configurable reliable messaging system
US20040153700A1 (en) * 2003-01-02 2004-08-05 Nixon Mark J. Redundant application stations for process control systems
US7251745B2 (en) * 2003-06-11 2007-07-31 Availigent, Inc. Transparent TCP connection failover
US7386624B2 (en) * 2003-10-23 2008-06-10 International Business Machines Corporation Method, system and article for dynamic real-time stream aggregation in a network
US7401256B2 (en) * 2004-04-27 2008-07-15 Hitachi, Ltd. System and method for highly available data processing in cluster system
US20050254508A1 (en) * 2004-05-13 2005-11-17 Nokia Corporation Cooperation between packetized data bit-rate adaptation and data packet re-transmission
US20050283529A1 (en) * 2004-06-22 2005-12-22 Wan-Yen Hsu Method and apparatus for providing redundant connection services
EP1719056A4 (en) * 2004-08-26 2009-04-08 Availigent Inc Method and system for providing high availability to computer applications
US20060129666A1 (en) * 2004-12-09 2006-06-15 International Business Machines Corporation Selective device reset method for device sharing with fail-over
JP4516439B2 (en) * 2005-02-01 2010-08-04 富士通株式会社 Relay program, relay method, and relay device
US7668962B2 (en) * 2005-02-07 2010-02-23 Symantec Operating Corporation System and method for connection failover using redirection
JP2007312227A (en) * 2006-05-19 2007-11-29 Canon Inc Information processing system and its control method, and program executing the control method
US9009327B2 (en) * 2007-08-03 2015-04-14 Citrix Systems, Inc. Systems and methods for providing IIP address stickiness in an SSL VPN session failover environment

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1892921A2 (en) 2000-10-26 2008-02-27 Intel Corporation Method and sytem for managing distributed content and related metadata
US20020087912A1 (en) 2000-12-29 2002-07-04 International Business Machines Corporation Highly available TCP systems with fail over connections
EP1231756A2 (en) * 2001-02-06 2002-08-14 Hewlett-Packard Company, A Delaware Corporation Method and system for maintaining connections in a network
US20050086342A1 (en) * 2003-09-19 2005-04-21 Andrew Burt Techniques for client-transparent TCP migration
US20070198710A1 (en) * 2004-12-30 2007-08-23 Xstor Systems, Inc. Scalable distributed storage and delivery

Also Published As

Publication number Publication date
EP2274898B1 (en) 2014-04-30
CN102047643A (en) 2011-05-04
US20090254775A1 (en) 2009-10-08
BRPI0911284A2 (en) 2016-07-26
JP5695558B2 (en) 2015-04-08
CN102047643B (en) 2015-01-28
CA2706579A1 (en) 2009-10-08
EP2274898A1 (en) 2011-01-19
BRPI0911284B1 (en) 2021-03-02
KR101419579B1 (en) 2014-07-14
US7971099B2 (en) 2011-06-28
KR20100135855A (en) 2010-12-27
CA2706579C (en) 2016-07-19
JP2011518486A (en) 2011-06-23

Similar Documents

Publication Publication Date Title
CA2706579C (en) Method for enabling faster recovery of client applications in the event of server failure
JP4851585B2 (en) COMMUNICATION METHOD FOR SYSTEM COMPRISING CLIENT DEVICE AND MULTIPLE SERVER DEVICE, ITS COMMUNICATION PROGRAM, CLIENT DEVICE, AND SERVER DEVICE
US7797565B1 (en) System and method for maintaining communication protocol connections during failover
US7532577B2 (en) Managing transmission control protocol (TCP) connections
US6934875B2 (en) Connection cache for highly available TCP systems with fail over connections
US7929422B2 (en) Method of moving a transport connection among network hosts
US6871296B2 (en) Highly available TCP systems with fail over connections
CA2547880C (en) Improved distributed kernel operating system
JP2004032224A (en) Server takeover system and method thereof
EP1859594B1 (en) Server side tftp flow control
KR101363167B1 (en) Improved distributed kernel operating system
US6934768B1 (en) Dynamic modification of fragmentation size cluster communication parameter in clustered computer system
WO2015119934A1 (en) System and method for reliable multicast data transport
JP2001514773A (en) Reliable event delivery system
KR20130096297A (en) Method and system for client recovery strategy in a redundant server configuration
WO2007065243A1 (en) A method for detecting non-responsive applications in a tcp-based network
EP3873067A1 (en) Data transmission method and apparatus
EP2597818A1 (en) Cluster management system and method
CN113986501A (en) Real-time database API (application program interface) uninterrupted calling method, system, storage medium and server
JPH09160858A (en) Data resending method and server
WO2012132101A1 (en) Information processing device, and failure response program
CN115801642A (en) RDMA communication management module, method, device and medium based on state control
CN106230747B (en) Method, device and system for recovering TCP connection sequence number
Cisco SNASW
Cisco Stream Control Transmission Protocol (SCTP) Release 2

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200980120431.9

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09729022

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2706579

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 5088/CHENP/2010

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2011502320

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20107024139

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2009729022

Country of ref document: EP

REG Reference to national code

Ref country code: BR

Ref legal event code: B01E

Ref document number: PI0911284

Country of ref document: BR

ENP Entry into the national phase

Ref document number: PI0911284

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20101001