Dynamic load balancing of a network of client and server computer

• US 6,886,035 B2
• Filed: 05/13/2002
• Issued: 04/26/2005
• Est. Priority Date: 08/02/1996
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Wolff, James J.
• Primary Examiner(s): Barot, Bharat
• Application Number:
  US10/145,423
• Publication Number:
  US 20030126200A1
• Time in Patent Office: 1,079 Days
• Field of Search: 709200-203, 709205-206, 709217-219, 709223-229, 709/235, 709238-239, 718102-105
• US Class Current: 709/219
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores

Abstract

Methods for load rebalancing by clients in a network are disclosed. Client load rebalancing allows the clients to optimize throughput between themselves and the resources accessed by the nodes. A network, which implements this embodiment of the invention, can dynamically rebalance itself to optimize throughput by migrating client I/O requests from over_utilized pathways to under_utilized pathways. Client load rebalancing allows a client to re-map a path through a plurality of nodes to a resource. The re-mapping may take place in response to a redirection command from an overloaded node.

Claims

1. A method for load balancing a network, the network comprising a number of server computers that serve I/O requests directed by a number of client computers to resources via the server computers, each server computer receiving I/O requests from client computers, the resources initially served by at least two server computers, each resource associated with an administrative server computer that carries out an administrative portion of each I/O request directed to the resource, the method comprising:

receiving at a first server computer an I/O request directed to a resource;

carrying out the I/O request by the first server computer and, when the first server computer is not an administrative server computer for the resource, by an administrative computer assigned to the resource;

determining by the first server computer that the first server computer has exceeded a utilization threshold; and

re-directing by the first server computer subsequent I/O requests directed to the resource by at least one client computer to an alternate server computer that serves I/O requests for the resource, wherein the at least one client computer needs to send the subsequent I/O requests directly to the alternate server computer.

2. The method of claim 1 wherein the I/O request is a read request for obtaining a data set on the resource.

3. The method of claim 1 wherein determining that the first server has exceeded a utilization threshold is performed on at least one of the client computer and the first server computer.

4. The method of claim 1 wherein re-directing subsequent I/O requests directed to the resource by at least one client computer to an alternate server computer that serves I/O requests for the resource is performed by at least one of the client computer and the first server computer.

5. The method of claim 1 wherein determining that the first server has exceeded a utilization threshold further comprises:

determining that the first server computer has exceeded a utilization threshold, wherein the utilization threshold comprises at least one of a fixed threshold utilization and a calculated threshold utilization.

6. The method of claim 5 wherein the utilization threshold is one of:

a percentage of the I/O bandwidth of the first server computer; and

a percentage of the processing capacity of the first server computer.

7. The method of claim 5 wherein re-directing subsequent I/O requests directed to the resource by at least one client computer to an alternate server computer that serves I/O requests for the resource further comprises:

determining a second server computer that serves the resource;

ascertaining that utilization of the first server computer exceeds utilization of the second server computer;

sending a redirect message from the first server computer to the client computer containing an indication of the second server computer;

receiving the redirect message by the client computer; and

altering state information on the client computer to direct subsequent I/O requests to the second server computer.

8. The method of claim 1 wherein determining that the first server has exceeded a utilization threshold further comprises:

tracking each of the number of server computers to determine a utilization for each of the number of server computers;

detecting a second server computer that serves I/O requests directed to the resource;

ascertaining that utilization of the second server computer is less than utilization of the first server computer; and

re-directing subsequent I/O requests from the client computer directed to the resource to the second server computer.

9. The method of claim 8, wherein tracking each of the number of server computers to determine a utilization for each of the number of server computers further comprises:

determining for each of the number of server computers a corresponding utilization; and

updating for each of the number of server computers a corresponding entry in a file for storing utilization indications for the network.

10. The method of claim 9 wherein ascertaining that utilization of the second server computer is less than utilization of the first server computer further comprises:

reading the file to detect that utilization of the second server computer is less than utilization of the first server computer.

11. The method of claim 10 wherein a corresponding entry in a file for storing utilization indications for the network is periodically updated at an interval recorded in the file.

12. The method of claim 1 further comprising:

forming a single system image by the client computer showing all available paths through the number of server computers to the resource.

13. The method of claim 12 wherein re-directing subsequent I/O requests directed to the resource by at least one client computer to an alternate server computer that serves I/O requests for the resource further comprises:

correlating, in the single system image, the resource with indications of all corresponding server computers that serve I/O requests directed to the resource;

tagging each of the indications of corresponding server computers with a time tag indicating a time at which a redirect command was last received by the client computer from the server computer; and

selecting as the alternate server computer the server computer having an indication tagged with a time tag earlier in time than the other indications of server computer.

14. The method of claim 13 further comprising:

updating the single system image to exclude from among the indications of server computers those server computers that become unavailable for serving I/O requests and to include within the indications of server computers those server computers that becomes available for serving I/O requests.

15. A computer usable medium having computer readable program code for carrying out the load balancing method of claim 1.

16. A method for recovering from server computer failures in a network, the network comprising a number of server computers that serve I/O requests directed by a number of client computers to resources via the server computers, the resources initially served by at least two server computers, each resource associated with an administrative server computer that carries out an administrative portion of each I/O request directed to the resource, the method comprising:

sending an I/O request directed to a resource from a client computer to a first server computer;

determining that an I/O failure occurred on the first server computer; and

re-directing subsequent I/O requests directed to the resource from the client computer to an alternate computer, wherein the client computer needs to send the subsequent I/O requests directly to the alternate computer.

17. The method of claim 16 further comprising:

forming a single system image at the client computer showing all available paths through the number of server computers to the resource; and

updating the single system image to exclude from all available paths those paths that include the first server computer.

18. The method of claim 17 further comprising:

updating the single system image to include among the available paths all paths that include the first server computer when the first server computer becomes available.

19. The method of claim 18 further comprising the acts of:

correlating, in the single system image, the resource with indications of all corresponding server computers that serve I/O requests directed to the resource;

tagging each of the indications of corresponding server computers with a time tag indicating a time at which a redirect command was last received by the client computer from the server computer; and

selecting as the alternate server computer the server computer having an indication tagged with a time tag earlier in time than the other indications of server computer.