Load balancing system

• US 20040098499A1
• Filed: 11/05/2003
• Published: 05/20/2004
• Est. Priority Date: 11/05/2002
• Status: Abandoned Application

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: Tamai, Hiroaki
• Application Number:
  US10/701,926
• Publication Number:
  US 20040098499A1
• Time in Patent Office: Days
• US Class Current: 709/232
• 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/1014 based on the content of a request

Abstract

A load balancing system provided with at least one first load balancing apparatus for analyzing higher layer information included in a received packet to generate attribute information of the received packet and transmitting the packet given that attribute information, a second load balancing apparatus for determining an optimal server for allocation of the packet based on traffic status information of packets and the attribute information sent from the at least one first load balancing apparatus and transmitting the packet to the server, and, optionally, a third load balancing apparatus for allocating the received packet to any of a plurality of first load balancing apparatuses, whereby it becomes possible to reduce as much as possible the intercommunication required for load balancing in the system and to obtain a performance proportional to the number of load balancing apparatuses.

Claims

1. A load balancing system provided with:

at least one first load balancing apparatus which analyzes higher layer information included in a received packet received from a client side to generate attribute information of the received packet and transmits the packet with the attribute information attached and

a second load balancing apparatus which monitors a state of traffic of packets transmitted to servers connected under it in correspondence with the servers, determines an optimum server for allocation of each packet based on the traffic state information and the attribute information transmitted from the corresponding first load balancing apparatus, and transmits the packet to the determined server.

2. A load balancing system as set forth in claim 1, comprising a plurality of first load balancing apparatuses and a second load balancing apparatus shared by the plurality of first load balancing apparatuses and further provided with a third load balancing apparatus for allocating said received packet in accordance with a predetermined algorithm to any of said plurality of first load balancing apparatuses.

3. A load balancing system as set forth in claim 1, wherein:

said first load balancing apparatus has a packet analyzing means,

said packet analyzing function unit generates identification information for identifying an application by said higher layer information and discrimination information for discriminating a series of transactions relating to the application, generates end information when the series of transactions ends, attaches the information to said received packet, and transmits the result to the second load balancing apparatus.

4. A load balancing system as set forth in claim 3, wherein said packet analyzing function unit assigns said discrimination information to said packet each time a series of transactions is started, uses the same discrimination information while a series of transactions is in progress, and releases said discrimination information when said series of transactions ends.

5. A load balancing system as set forth in claim 3, wherein:

said second load balancing apparatus has a server selecting function unit,

which server selecting means acquires statistical information relating to a flow rate of packets and a number of transactions as said traffic status information, identifies a group of servers able to execute said application based on the received identification information, determines the optimum destination server in the group of servers based on the statistical information, and sends the received packet to the destination server.

6. A load balancing system as set forth in claim 5, wherein said server selecting function unit acquires degeneration/restoration information relating to degeneration and restoration of the servers and excludes degenerating servers from coverage in the determination of the said destination server.

7. A load balancing system as set forth in claim 5, wherein said server selecting function unit determines said destination server from said discrimination information in accordance with whether a series of transactions has started, is in progress, or has ended.

8. A load balancing system as set forth in claim 5, wherein said server selecting function unit updates said traffic status information in accordance with any change in the traffic status.

9. A load balancing system as set forth in claim 3, wherein said server selecting function unit transmits a packet to the server side after stripping the attribute information, identification information, and end information added to the received packet.

10. A load balancing system as set forth in claim 6, wherein said server selecting function unit has various types of tables for storing various types of information required for identification of said group of servers and determination of said destination server.

11. A load balancing system as set forth in claim 10, wherein:

said various types of tables include a first table,

said first table indicates correspondence between said discrimination information finished being assigned and said destination servers starting said transactions.

12. A load balancing system as set forth in claim 11, wherein said correspondence is deleted from said first table when said end information is ON.

13. A load balancing system as set forth in claim 10, wherein:

said various types of tables include a second table,

said second table indicates correspondence between said identification information and said servers able to process said application.

14. A load balancing system as set forth in claim 13, which refers to said second table when said received packet has not yet been assigned said discrimination information.

15. A load balancing system as set forth in claim 13, wherein said second table also indicates said degeneration/restoration information of said servers able to process said application corresponding to said servers.

16. A load balancing system as set forth in claim 13, wherein said second table also indicates weighting information designating said statistical information to be stressed on a priority basis when determining said optimal destination server corresponding to said identification information.

17. A load balancing system as set forth in claim 10, wherein:

said various types of tables include a third table,

said third table indicates said statistical information corresponding to said destination servers and refers to the statistical information to assign a destination server with a small processing load when determining the optimal destination server.

18. A load balancing system as set forth in claim 17, wherein said third table is referred to when there is correspondence between said discrimination information finished being assigned and said destination server starting said transaction.

19. A load balancing system as set forth in claim 17, wherein said third table further indicates an identification information list corresponding to said destination servers and registers processable applications and data attributes for each destination server in said identification information list.