Dynamic load balancing of a network of client and server computers

• US 6,185,601 B1
• Filed: 04/15/1998
• Issued: 02/06/2001
• 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 Company (HP Inc.)
• Inventors: Wolff, James J.
• Primary Examiner(s): Matar, Ahmad F.
• Assistant Examiner(s): Barot, Bharat
• Application Number:
  US09/060,869
• Time in Patent Office: 1,028 Days
• Field of Search: 709/102-105, 709/201-203, 709/205-206, 709/217-219, 709/223-229, 709/235, 709/239
• US Class Current: 709/203
• CPC Class Codes: G06F 16/10 File systems; File servers

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 sever 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 by detecting at the client computer a delay in carrying out, by the first server computer, the I/O request directed to the resource; and

re-directing by the first server computer subsequent I/O requests directed to the resource by at lest one client computer to an alternate server computer that serves I/O requests for the resource.

2. 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 further comprises:

determining by the client computer a second server computer that serves the resource;

ascertaining by the client computer that utilization of the first server computer exceeds utilization of the second server computer; and

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

3. 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 computer, 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:

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

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

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 at 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.

4. The method of claim 3 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 resources 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 re-direct command was last received by the client computer from the server computer; and

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

5. The method of claim 4 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 become available for serving I/O requests.

6. 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 from 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:

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

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

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

re-directing subsequent I/O requests directed to the resource in the client computer to an alternate computer; and

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

7. The method of claim 6 further comprising:

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

8. The method of claim 7 further comprising:

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 re-direct command was last received by the computer from the server computer; and

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