Splicing Persistent Connections

• US 20130117455A1
• Filed: 07/05/2012
• Published: 05/09/2013
• Est. Priority Date: 02/26/2001
• Status: Abandoned Application

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Incorporated
• Inventors: Shabtay, Lior, Beiser, Dan, Friedman, Ofir, Amitai, Eyal, Kronental, Guy
• Application Number:
  US13/542,633
• Publication Number:
  US 20130117455A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1014 based on the content of a request
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/163 In-band adaptation of TCP data exchange; In-band control procedures
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A method of connecting a client to a server by a load balancer associated with a plurality of servers. The method includes establishing a first connection for transmission of packets between the load balancer and the client, selecting a server to service the client, and splicing the first connection with a second connection between the load balancer and the selected server, the second connection being established before the first connection.

Claims

1-36. -36. (canceled)

37. A method of connecting a client to a server by a load balancer associated with a plurality of servers, the method comprising:

establishing a first connection for transmission of packets between the load balancer and the client;

selecting a server from the plurality of servers to service the client; and

splicing the first connection with a second connection between the load balancer and the selected server, the second connection being established before the first connection;

wherein the load balancer monitors numbers of available connections between the load balancer and each server in the plurality of servers, the available connections being connections which are not spliced with connections to clients, and if the number of available connections for a given one of the plurality of servers falls outside of a predetermined range established by the load balancer for the given server, the load balancer opens one or more new connections with the given server or closes one or more existing connections with the given server so as to maintain the number of available connections for the server within the predetermined range; and

wherein the predetermined range for each server in the plurality of servers is responsive to the rate at which each server receives requests.

38. A method according to claim 37, wherein selecting the server comprises selecting a server responsive to contents of an HTTP request transmitted on the first connection.

39. A method according to claim 37, wherein selecting the server comprises selecting a server responsive to a number of available connections between the load balancer and one or more of the servers with which the load balancer is associated.

40. A method according to claim 39, wherein selecting the server comprises selecting a server which has at least one available connection with the load balancer.

41. A method according to claim 37, comprising disconnecting the splicing of the first and second connections and splicing the second connection with a third connection established between the load balancer and the client.

42. A method according to claim 41, wherein the first and third connections are formed between the load balancer and the same client.

43. A method according to claim 41, wherein the first and third connections are formed between the load balancer and different clients.

44. A method according to claim 41, comprising closing the first connection substantially concurrently with disconnecting the splicing of the first and second connections.

45. A method according to claim 41, comprising splicing the first connection to a fourth connection which connects the load balancer to a server.

46. A method according to claim 45, wherein the fourth connection comprises a previously established connection.

47. A method according to claim 37, comprising examining contents of packets transmitted on the first connection to determine when a new request is transmitted on the first connection.

48. A method according to claim 47, comprising selecting a server to service the new request and splicing the first connection to a connection leading to the server selected to service the new request.

49. A method according to claim 48, wherein splicing the first connection to a connection leading to the server selected to service the new request comprises continuing the splicing of the first connection and a currently spliced connection, if the current connection spliced to the first connection leads to the server selected to service the new request.

50. A method according to claim 48, wherein splicing the first connection to a connection leading to the server selected to service the new request comprises disconnecting the current splicing of the first connection and splicing the first connection to a connection leading to the server selected to service the new request, if the current connection spliced to the first connection does not lead to the server selected to service the new request.

51. A method according to claim 50, wherein disconnecting the current splicing of the first connection comprises examining the contents of packets transmitted on the first connection to determine when a response to a previous request was transmitted on the connection and disconnecting the current splicing only after the entire response was transmitted to the client.

52. A method according to claim 50, wherein disconnecting the current splicing of the first connection comprises disconnecting the current splicing only after receiving from the client acknowledgement of receipt of the entire response.

53. A method according to claim 48, wherein selecting a server to service the new request gives preference to the server to which the connection currently spliced to the first connection leads.

54. A method according to claim 37, wherein the first and second connections comprise TCP connections.

55. A method according to claim 37, wherein monitoring numbers of available connections comprises monitoring such that the number of available connections for the given server is equal to a predetermined number except during short transient periods, when the total number of connections handled by the given server is below a predetermined maximal number of connections allowed by the given server.

56. A method according to claim 37, wherein the predetermined range is different for at least two of the plurality of servers.