Apparatus and method for distributing requests across a cluster of application servers

• US 20060129684A1
• Filed: 11/10/2004
• Published: 06/15/2006
• Est. Priority Date: 11/10/2004
• Status: Abandoned Application

• Current Assignee: Chutney Technologies (Cisco Systems, Inc.)
• Original Assignee: Chutney Technologies (Cisco Systems, Inc.)
• Inventors: Datta, Anindya
• Application Number:
  US10/985,118
• Publication Number:
  US 20060129684A1
• Time in Patent Office: Days
• US Class Current: 709/229
• 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/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• 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 method and apparatus for distributing a plurality of session requests across a plurality of servers. The method includes receiving a session request and determining whether the received request is part of an existing session. If the received request is determined not to be part of an existing session, then the request is directed to a server having the lowest expected load. If, however, the request is determined to be part of an existing session, then a second determination is made as to whether the server owning the existing session is in a dispatchable state. If the server is determined to be in a dispatchable state, then the request is directed to that server. However, if the server is determined not to be in a dispatchable state, then the request is directed to a server other than the one owning the existing session that has the lowest expected load.

Claims

1. A method for distributing a plurality of session requests across a plurality of servers, the method comprising the steps of:

receiving at least one session request;

determining whether the received session request is part of an existing session; and

if so, determining whether the server owning the existing session to which the session request is part of is in a dispatchable state,

if so, directing the session request to the server owning the existing session to which the session request is part of, and

if not, directing the session request to a server that does not own the existing session to which the session request is part of and that has the lowest expected load,

if not, directing the session request to a server that has the lowest expected load.

2. The method as recited in claim 1, wherein the step of directing the session request to a server that has the lowest expected load further comprises the steps of:

obtaining a load metric for more than one of the plurality of servers,

comparing the load metrics of the plurality of servers, and

determining which server of the plurality of servers has the lowest expected load based on the comparison of the load metrics of the plurality of servers.

3. The method as recited in claim 2, wherein, if the received session request is the first request of a session, the obtained load metric for the plurality of servers further comprises a modified load metric, wherein the modified load metric is an actual load of the server modified by a factored expected load value.

4. The method as recited in claim 3, wherein, if the expected load value has been estimated inaccurately, the expected load value is updated and the modified load value is updated based on the updated expected load value.

5. The method as recited in claim 2, wherein, if the received session request is part of an existing session, the obtained load metric for the plurality of servers further comprises an actual load value of the server for the current time period.

6. The method as recited in claim 1, wherein the second determining step further comprises the steps of:

obtaining an actual load of the server owning the existing session,

retrieving a maximum acceptable load of the server owning the existing session,

comparing the actual load of the server to the maximum acceptable load of the server, and

determining whether the server is in a dispatchable state based on the comparison of the actual load of the server to the maximum acceptable load of the server.

7. The method as recited in claim 1, wherein the received session request has associated therewith at least one session object, and wherein the method further comprises the step of replicating the session objects associated with the received session request in a server other than the server owning the existing session.

8. The method as recited in claim 1, wherein the received session request has associated therewith at least one session object, and wherein the method further comprises the step of storing the session objects associated with the received session request in a centralized repository.

9. The method as recited in claim 1, wherein the received session request has associated therewith a user and wherein the existing session has associated therewith a user, and wherein the first determining step further comprises determining whether the user associated with the received session request and the user associated with the existing session are the same user.

10. The method as recited in claim 1, wherein the first determining step further comprises determining whether the received session request is the first request of/in a session.

11. The method as recited in claim 1, wherein the plurality of servers further comprises a cluster of application servers, and wherein at least one of the plurality or session requests further comprises an application request.

12. An apparatus for distributing a plurality of session requests across a plurality of servers, the apparatus comprising:

logic configured to determine whether the received session request is part of an existing session, and if not, directing the session request to a different server that has a lowest expected load, and if so, said logic making a second determination by determining whether the server owning the existing session is in a dispatchable state, and if so, directing the session request to said server, and wherein if a determination is made that said server is not in a dispatchable state, directing the session request to a different server that has a lowest expected load.

13. The apparatus as recited in claim 12, wherein the logic further

obtains a load metric for more than one of the plurality of servers,

compares the load metrics of the plurality of servers, and

determines which server of the plurality of servers has the lowest expected load based on the comparison of the load metrics of the plurality of servers.

14. The apparatus as recited in claim 12, wherein the logic further:

obtains an actual load of the server owning the existing session,

retrieves a maximum acceptable load of the server owning the existing session,

compares the actual load of the server to the maximum acceptable load of the server, and

determines whether the server is in a dispatchable state based on the comparison of the actual load of the server to the maximum acceptable load of the server.

15. The apparatus as recited in claim 12, further comprising an application analyzer module for characterizing the behavior of at least one of the plurality of servers by measuring the throughput and/or the peak load level of the server.

16. The apparatus as recited in claim 12, further comprising a request dispatcher for monitoring the actual load and/or the expected load of the server.

17. A computer program for distributing a plurality of session requests across a plurality of servers, the computer program being embodied on a computer readable medium, the program comprising:

code for receiving at least one session request;

code for determining whether the received session request is part of an existing session; and

if so, code for determining whether the server owning the existing session to which the session request is part of is in a dispatchable state,

if so, code for directing the session request to the server owning the existing session to which the session request is part of, and

if not, code for directing the session request to a server that does not own the existing session to which the session request is part of and that has the lowest expected load,

if not, code for directing the session request to a server that has the lowest expected load.

18. The computer program as recited in claim 17, further comprising code for

obtaining a load metric for more than one of the plurality of servers,

comparing the load metrics of the plurality of servers, and

determining which server of the plurality of servers has the lowest expected load based on the comparison of the load metrics of the plurality of servers.

19. The computer program as recited in claim 17, further comprising code for

obtaining an actual load of the server owning the existing session,

retrieving a maximum acceptable load of the server owning the existing session,

comparing the actual load of the server to the maximum acceptable load of the server, and

determining whether the server is in a dispatchable state based on the comparison of the actual load of the server to the maximum acceptable load of the server.

20. A web application infrastructure, comprising:

a plurality of servers; and

at least one computer, connected to the plurality of servers, for distributing a plurality of session requests across the plurality of servers, the at least one computer having;

at least one processor,

a memory device coupled to the at least one processor for storing at least one set of instructions to be executed, and

an input device coupled to the at least one processor and the memory device for receiving input data including the plurality of session requests,

wherein the at least one computer is operative to execute the at least one set of instructions, and the at least one set of instructions stored in the memory device in the at least one computer causing the at least one processor associated therewith to;

determine whether the received session request is part of an existing session; and

if so, determine whether the server owning the existing session to which the session request is part of is in a dispatchable state,

if so, direct the session request to the server owning the existing session to which the session request is part of,

if not, direct the session request to a server that does not own the existing session to which the session request is part of and that has the lowest expected load,

if not, direct the session request to a server that has the lowest expected load.

21. The system as recited in claim 20, wherein the instructions stored in the memory device in the computer further cause the at least one processor to:

obtain a load metric for more than one of the plurality of servers,

compare the load metrics of the plurality of servers, and

determine which server of the plurality of servers has the lowest expected load based on the comparison of the load metrics of the plurality of servers.

22. The system as recited in claim 20, wherein the instructions stored in the memory device in the computer further cause the at least one processor to:

obtain an actual load of the server owning the existing session,

retrieve a maximum acceptable load of the server owning the existing session,

compare the actual load of the server to the maximum acceptable load of the server, and

determine whether the server is in a dispatchable state based on the comparison of the actual load of the server to the maximum acceptable load of the server.

23. The system as recited in claim 20, wherein at least one of the plurality of servers and/or the at least one computer includes an application analyzer module for characterizing the behavior of at least one of the plurality of servers by measuring the throughput and/or the peak load level of the server.

24. The system as recited in claim 20, wherein at least one of the plurality of servers and/or the at least one computer includes a request dispatcher for monitoring the actual load and/or the expected load of the server.

25. The system as recited in claim 20, wherein at least a portion of the at least one computer resides in at least one of the plurality of servers.

26. The system as recited in claim 20, wherein the plurality of servers further comprises a cluster of application servers.

27. The system as recited in claim 20, wherein the plurality of servers further comprises:

a cluster of web servers, and

a cluster of application servers in communication with the cluster of web servers.