Distributed and Replicated Sessions on Computing Grids

• US 20070150602A1
• Filed: 10/04/2006
• Published: 06/28/2007
• Est. Priority Date: 10/04/2005
• Status: Abandoned Application

• Current Assignee: WaveMaker Software, Inc. (Broadcom, Inc.)
• Original Assignee: WaveMaker Software, Inc. (Broadcom, Inc.)
• Inventors: Yared, Peter, Norton, Jeffrey
• Application Number:
  US11/538,692
• Publication Number:
  US 20070150602A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• 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/1017 based on a round robin mechanism
• 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

Abstract

Distributed and replicated sessions are implemented in a grid architecture. A session including conversational state is stored at a server in the grid. An incoming request is directed to a server via a load balancing mechanism. When a server receives an incoming request, it either a) retrieves the session from the server that currently holds the state, or b) forwards the request to the server that currently holds the session. Each server maintains the session for the requests that it has serviced until relieved of this responsibility by another server. A server holding a session is relieved of responsibility for the state when another server retrieves the session. In one aspect of the invention, each session is replicated among a number of servers, so as to provide additional redundancy and thereby avoid having any single server as a single point of failure for the session which it maintains.

Claims

1. A method for maintaining session state information in a multiple server architecture, comprising:

receiving an initial request from a client;

directing the initial request to a first server within a plurality of servers;

creating a session for the client;

storing the client session at a storage device associated with the first server;

transmitting, to the client, a server identifier identifying the first server as the holder of the session;

receiving a subsequent request from the client, the subsequent request comprising the server identifier identifying the first server;

directing the subsequent request to a second server within a plurality of servers;

at the second server, reading the server identifier; and

responding to the request using the session stored at the server identified by the server identifier.

2. The method of claim 1, wherein responding to the request using the session stored at the server identified by the server identifier comprises:

the second server retrieving, from the server identified by the server identifier, the session.

3. The method of claim 2, further comprising:

storing the client session at a storage device associated with the second server; and

transmitting, to the client, a server identifier identifying the second server as the holder of the session.

4. The method of claim 1, wherein responding to the request using the session stored at the server identified by the server identifier comprises:

redirecting the subsequent request to the server identified by the server identifier.

5. The method of claim 1, wherein responding to the request using the session stored at the server identified by the server identifier comprises:

determining whether to retrieve the session from the server identified by the server identifier or to redirect the subsequent request to the server identified by the server identifier; and

performing the determined action.

6. The method of claim 5, wherein determining whether to retrieve or redirect comprises at least one of:

determining whether the session size exceeds the request size; and

determining whether the session size exceeds the sum of the request size and an expected reply size.

7. The method of claim 1, wherein:

directing the initial request to a first server within a plurality of servers comprises directing the initial request using a load balancing method based on at least one of network conditions and round robin allocation; and

directing the subsequent request to a second server within a plurality of servers comprises directing the subsequent request using a load balancing method based on at least one of network conditions and round robin allocation.

8. The method of claim 1, wherein the plurality of servers comprises a grid.

9. The method of claim 1, wherein transmitting the server identifier comprises transmitting a representation of the server identifier for storage at the client.

10. The method of claim 1, wherein transmitting the server identifier comprises transmitting a representation of the server identifier for storage in a cookie at the client.

11. The method of claim 1, wherein the server identifier comprises an encoded IP address.

12. A method for storing session state information in a multiple server architecture, comprising:

receiving an initial request from a client;

directing the initial request to a selected server within a plurality of servers;

creating a session for the client;

storing the client session at a storage device associated with the selected server;

transmitting, to the client, a server identifier identifying the selected server as the holder of the session.

13. The method of claim 12, wherein:

directing the initial request to a selected server within a plurality of servers comprises directing the initial request based on at least one of a load balancing method based on network conditions and a round robin allocation method.

14. The method of claim 12, wherein the plurality of servers comprises a grid.

15. The method of claim 12, wherein transmitting the server identifier comprises transmitting a representation of the server identifier for storage at the client.

16. The method of claim 12, wherein transmitting the server identifier comprises transmitting a representation of the server identifier for storage in a cookie at the client.

17. The method of claim 12, wherein the server identifier comprises an encoded IP address.

18. A method for retrieving session state information in a multiple server architecture, comprising:

receiving a request from a client, the request comprising a server identifier identifying a first server as a holder of the session;

directing the request to a second server;

at the second server, reading the server identifier; and

responding to the request using the session stored at the identified first server.

19. The method of claim 18, wherein responding to the request using session comprises:

the second server retrieving the session from the server identified by the server identifier.

20. The method of claim 19, further comprising:

storing the session at a storage device associated with the second server; and

transmitting, to the client, a server identifier identifying the second server as the holder of the session.

21. The method of claim 18, wherein responding to the request using the session stored at the identified first server comprises:

redirecting the request to the identified first server.

22. The method of claim 18, wherein responding to the request using the session stored at the identified first server comprises:

determining whether to retrieve the session from the identified first server or to redirect the subsequent request to the identified first server; and

performing the determined action.

23. The method of claim 22, wherein determining whether to retrieve or redirect comprises at least one of:

determining whether the session size exceeds the request size; and

determining whether the session size exceeds the sum of the request size and an expected reply size.

24. The method of claim 18, wherein:

directing the request to a second server comprises directing the request using at least one of a load balancing method based on network conditions and a round robin allocation.

25. The method of claim 18, wherein the first and second servers are part of a grid.

26. The method of claim 18, wherein the server identifier is derived from information stored at the client.

27. The method of claim 18, wherein the server identifier is derived from information in a cookie at the client.

28. The method of claim 18, wherein the server identifier comprises an encoded IP address.

29. A method for maintaining session state information in a multiple server architecture, comprising:

receiving an initial request from a client;

directing the initial request to a first server within a plurality of servers;

creating a session for the client;

storing the client session at a storage device associated with the first server;

storing a copy of the client session at at least one additional storage device associated with at least one additional server;

transmitting, to the client, a plurality of server identifiers, the server identifiers identifying the first server and the at least one additional server as the holders of the session;

receiving a subsequent request from the client, the subsequent request comprising the server identifiers identifying the first server and the at least one additional server;

directing the subsequent request to a second server within the plurality of servers;

at the second server, reading the server identifiers; and

responding to the request using the session stored at a server identified by one of the server identifiers.

30. The method of claim 29, wherein responding to the request using the stored session comprises:

the second server retrieving the session from one of the servers identified by the server identifiers.

31. The method of claim 30, further comprising:

storing the session at a storage device associated with the second server; and

storing, at at least one additional storage device associated with at least one additional server, a copy of the client session;

transmitting, to the client, server identifiers identifying the second server and the at least one additional server as the holders of the session.

32. The method of claim 29, wherein responding to the request using the session comprises:

redirecting the subsequent request to a server identified by one of the server identifiers.

33. The method of claim 29, wherein responding to the request using the stored session comprises:

determining whether to retrieve the session from a server identified by one of the server identifiers or to redirect the subsequent request to a server identified by one of the server identifiers; and

performing the determined action.

34. The method of claim 33, wherein determining whether to retrieve or redirect comprises at least one of:

determining whether the session size exceeds the request size; and

determining whether the session size exceeds the sum of the request size and an expected reply size.

35. The method of claim 29, wherein:

directing the initial request to a first server within a plurality of servers comprises directing the initial request using at least one of a load balancing method based on network conditions and a round robin allocation method; and

directing the subsequent request to a second server within a plurality of servers comprises directing the subsequent request using at least one of a load balancing method based on network conditions and a round robin allocation method.

36. The method of claim 29, wherein the plurality of servers comprises a grid.

37. The method of claim 29, wherein transmitting the plurality of server identifiers comprises transmitting representations of the server identifiers for storage in a cookie at the client.

38. The method of claim 29, wherein each server identifier comprises an encoded IP address.

39. A method for storing session state information in a multiple server architecture, comprising:

receiving an initial request from a client;

directing the initial request to a first server within a plurality of servers;

creating a session for the client;

storing the client session at a storage device associated with the first server;

storing, at at least one additional storage device associated with at least one additional server, a copy of the client session;

transmitting, to the client, a plurality of server identifiers, the server identifiers identifying the first server and the at least one additional server as the holders of the session.

40. The method of claim 39, wherein:

directing the initial request to a first server within a plurality of servers comprises directing the initial request using at least one of a load balancing method based on network conditions and a round robin allocation method.

41. The method of claim 39, wherein the plurality of servers comprises a grid.

42. The method of claim 39, wherein transmitting the plurality of server identifiers comprises transmitting representations of the server identifiers for storage in a cookie at the client.

43. The method of claim 39, wherein each server identifier comprises an encoded IP address.

44. A method for retrieving session state information in a multiple server architecture, comprising:

receiving a request from a client, the request comprising a plurality of server identifiers identifying a plurality of servers as holders of a session;

directing the request to a server;

at the server, reading the plurality of server identifiers; and

responding to the request using a session stored at one of the identified servers.

45. The method of claim 44, wherein responding to the request using the session comprises:

the server retrieving the session from one of the identified servers.

46. The method of claim 45, further comprising:

storing the client session at a storage device associated with the server; and

storing, at at least one additional storage device associated with at least one additional server, a copy of the client session;

transmitting, to the client, server identifiers identifying the server and the at least one additional server as the holders of the session.

47. The method of claim 44, wherein responding to the request using the stored session comprises:

redirecting the request to a server identified by one of the server identifiers.

48. The method of claim 44, wherein responding to the request using the stored session comprises:

determining whether to retrieve the session from a server identified by one of the server identifiers or to redirect the subsequent request to a server identified by one of the server identifiers; and

performing the determined action.

49. The method of claim 48, wherein determining whether to retrieve or redirect comprises determining whether the session size exceeds the request size.

50. The method of claim 44, wherein:

directing the request to a server comprises directing the request using at least one of a load balancing method based on network conditions and a round robin allocation method.

51. The method of claim 44, wherein the plurality of servers comprises a grid.

52. The method of claim 44, wherein each server identifier comprises an encoded IP address.

53. A computer program product for maintaining session state information in a multiple server architecture, comprising:

a computer-readable medium; and

computer program code, encoded on the medium, for;

receiving an initial request from a client;

directing the initial request to a first server within a plurality of servers;

creating a session for the client;

storing the client session at a storage device associated with the first server;

transmitting, to the client, a server identifier identifying the first server as the holder of the session;

receiving a subsequent request from the client, the subsequent request comprising the server identifier identifying the first server;

directing the subsequent request to a second server within a plurality of servers;

at the second server, reading the server identifier; and

responding to the request using the session stored at the server identified by the server identifier.

54. A computer program product for maintaining session state information in a multiple server architecture, comprising:

a computer-readable medium; and

computer program code, encoded on the medium, for;

receiving an initial request from a client;

directing the initial request to a first server within a plurality of servers;

creating a session for the client;

storing the client session at a storage device associated with the first server;

storing a copy of the client session at at least one additional storage device associated with at least one additional server;

transmitting, to the client, a plurality of server identifiers, the server identifiers identifying the first server and the at least one additional server as the holders of the session;

receiving a subsequent request from the client, the subsequent request comprising the server identifiers identifying the first server and the at least one additional server;

directing the subsequent request to a second server within the plurality of servers;

at the second server, reading the server identifiers; and

responding to the request using the session stored at a server identified by one of the server identifiers.

55. A system for maintaining session state information in a multiple server architecture, comprising:

a load balancer, for;

receiving an initial request from a client and directing the initial request to a first server within a plurality of servers; and

receiving a subsequent request from the client, the subsequent request comprising the server identifier identifying the first server and directing the subsequent request to a second server within a plurality of servers;

a first server, for creating a session for the client and for transmitting, to the client, a server identifier identifying the first server as the holder of the session;

a storage device associated with the first server, for storing the client session; and

a second server, for reading the server identifier and responding to the request using the session stored at the first server.

56. A system for maintaining session state information in a multiple server architecture, comprising:

a load balancer, for;

receiving an initial request from a client and directing the initial request to a first server within a plurality of servers; and

receiving a subsequent request from the client, the subsequent request comprising the server identifiers identifying the first server and the at least one additional server and directing the subsequent request to a second server within the plurality of servers;

a first server, for creating a session for the client and for transmitting, to the client, a plurality of server identifiers, the server identifiers identifying the first server and at least one additional server as the holders of the session;

a storage device associated with the first server, for storing the client session;

at least one additional storage device associated with at least one additional server, for storing a copy of the client session; and

a second server for reading the server identifiers responding to the request using the session stored at a server identified by one of the server identifiers.