Technique for handling server session requests in a system having a plurality of servers

• US 7,113,993 B1
• Filed: 06/06/2002
• Issued: 09/26/2006
• Est. Priority Date: 06/20/2001
• Status: Expired due to Term

• Current Assignee: Microstrategy Incorporated
• Original Assignee: Microstrategy Incorporated
• Inventors: Cappiello, Scott, Le, Dyung V., Vinton, Patrick, Li, Benjamin Z., Li, Wenfeng, Du, Yi, Polana, Ramprasad
• Primary Examiner(s): Wiley, David
• Assistant Examiner(s): MANIWANG, JOSEPH R
• Application Number:
  US10/162,716
• Time in Patent Office: 1,573 Days
• Field of Search: 709/227, 709/228, 709/203, 718/105, 714/4
• US Class Current: 709/227
• 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/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• 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 technique for handling server session requests in a system having a plurality of servers is disclosed. In one embodiment, the technique includes receiving a request to create a session on one of the plurality of servers. In response to the request, a primary session is created on a first of the plurality of servers. After the primary session is created, at least one other of the plurality of servers are notified that the primary session has been created. Such notification allows for a backup session on the at least one other of the plurality of servers to take over for the primary session upon a failure on the first of the plurality of servers.

Claims

1. A method for handling a request to create a session on a server in a system having a plurality of servers, the method comprising the steps of:

receiving a request to create a session on one of the plurality of servers;

creating a primary session on a first of the plurality of servers in response to the request; and

notifying at least one other of the plurality of servers that the primary session has been created, such that a backup session on the at least one other of the plurality of servers may take over for the primary session upon a failure of the first of the plurality of servers, wherein the at least one other of the plurality of servers is notified that the primary session has been created prior to failure of the first of the plurality of servers.

2. The method as defined in claim 1, wherein the step of creating the primary session on the first of the plurality of servers includes the step of:

creating the primary session on the first of the plurality of servers based upon a pre-defined static distribution scheme.

3. The method as defined in claim 1, wherein the step of creating the primary session on the first of the plurality of servers includes the step of:

creating the primary session on the first of the plurality of servers based upon a relative load on each of the plurality of servers, the relative load on each of the plurality of servers being determined based upon a load metric associated with each of the plurality of servers.

4. The method as defined in claim 3, further comprising the step of:

determining the load metric associated with each of the plurality of servers based upon a number of requests that each of the plurality of servers has serviced over a period of time.

5. The method as defined in claim 3, further comprising the step of:

determining the load metric associated with each of the plurality of servers based upon a number of report jobs being processed by each of the plurality of servers at a particular point in time.

6. The method as defined in claim 3, further comprising the step of:

determining the load metric associated with each of the plurality of servers based upon a number of sessions that are open on each of the plurality of servers at a particular point in time.

7. The method as defined in claim 3, further comprising the step of:

determining the load metric associated with each of the plurality of servers based upon currently utilized or available resources on each of the plurality of servers at a particular point in time.

8. The method as defined in claim 1, further comprising the step of:

synchronizing information associated with the operation of the first of the plurality of servers with information associated with the operation of the at least one other of the plurality of servers.

9. A signal embodied in a carrier wave readable by a computing system and encoding a computer program of instructions for executing a computer process performing the method recited in claim 1.

10. A system for handling a request to create a session on a server in a system having a plurality of servers, the system comprising:

a user engine for receiving a request to create a session on one of the plurality of servers;

a load balancer for determining a first of the plurality of servers upon which a primary session should be created in response to the request; and

a synchronization module for notifying at least one other of the plurality of servers that the primary session has been created, such that a backup session on the at least one other of the plurality of servers may take over for the primary session upon a failure on the first of the plurality of servers, wherein the at least one other of the plurality of servers is notified that the primary session has been created prior to failure of the first of the plurality of servers.

11. The system as defined in claim 10, wherein the load balancer determines the first of the plurality of servers upon which the primary session should be created based upon a pre-defined static distribution scheme.

12. The system as defined in claim 10, wherein the load balancer determines the first of the plurality of servers upon which the primary session should be created based upon a relative load on each of the plurality of servers, the relative load on each of the plurality of servers being determined based upon a load metric associated with each of the plurality of servers.

13. The system as defined in claim 12, wherein the load balancer further determines the load metric associated with each of the plurality of servers based upon a number of requests that each of the plurality of servers has serviced over a period of time.

14. The system as defined in claim 12, wherein the load balancer further determines the load metric associated with each of the plurality of servers based upon a number of report jobs being processed by each of the plurality of servers at a particular point in time.

15. The system as defined in claim 12, wherein the load balancer further determines the load metric associated with each of the plurality of servers based upon a number of sessions that are open on each of the plurality of servers at a particular point in time.

16. The system as defined in claim 12, wherein the load balancer further determines the load metric associated with each of the plurality of servers based upon currently utilized or available resources on each of the plurality of servers at a particular point in time.

17. The system as defined in claim 10, wherein the synchronization module synchronizes information associated with the operation of the first of the plurality of servers with information associated with the operation of the at least one other of the plurality of servers.

18. An article of manufacture for handling a request to create a session on a server in a system having a plurality of servers, the article of manufacture comprising:

at least one processor readable carrier; and

instructions carried on the at least one carrier;

wherein the instructions are configured to be readable from the at least one carrier by at least one processor and thereby cause the at least one processor to operate so as to;

receive a request to create a session on one of the plurality of servers;

create a primary session on a first of the plurality of servers in response to the request; and

notify at least one other of the plurality of servers that the primary session has been created, such that a backup session on the at least one other of the plurality of servers may take over for the primary session upon a failure on the first of the plurality of servers, wherein the at least one other of the plurality of servers is notified that the primary session has been created prior to failure of the first of the plurality of servers.

19. The article of manufacture as defined in claim 18, wherein the instructions further cause the at least one processor to operate so as to:

create the primary session on the first of the plurality of servers based upon a pre-defined static distribution scheme.

20. The article of manufacture as defined in claim 18, wherein the instructions further cause the at least one processor to operate so as to:

create the primary session on the first of the plurality of servers based upon a relative load on each of the plurality of servers, the relative load on each of the plurality of servers being determined based upon a load metric associated with each of the plurality of servers.

21. The article of manufacture as defined in claim 20, wherein the instructions further cause the at least one processor to operate so as to:

determine the load metric associated with each of the plurality of servers based upon a number of requests that each of the plurality of servers has serviced over a period of time.

22. The article of manufacture as defined in claim 20, wherein the instructions further cause the at least one processor to operate so as to:

determine the load metric associated with each of the plurality of servers based upon a number of report jobs being processed by each of the plurality of servers at a particular point in time.

23. The article of manufacture as defined in claim 20, wherein the instructions further cause the at least one processor to operate so as to:

determine the load metric associated with each of the plurality of servers based upon a number of sessions that are open on each of the plurality of servers at a particular point in time.

24. The article of manufacture as defined in claim 20, wherein the instructions further cause the at least one processor to operate so as to:

determine the load metric associated with each of the plurality of servers based upon currently utilized or available resources on each of the plurality of servers at a particular point in time.

25. The article of manufacture as defined in claim 18, wherein the instructions further cause the at least one processor to operate so as to:

synchronize information associated with the operation of the first of the plurality of servers with information associated with the operation of the at least one other of the plurality of servers.