System and method to balance servers based on server load status

• US 10,447,775 B2
• Filed: 03/27/2018
• Issued: 10/15/2019
• Est. Priority Date: 09/30/2010
• Status: Active Grant

• Current Assignee: A10 Networks Incorporated
• Original Assignee: A10 Networks Incorporated
• Inventors: Kannan, Lalgudi Narayanan, Szeto, Ronald Wai Lun, Chen, Lee, Xu, Feilong, Jalan, Rajkumar
• Primary Examiner(s): Christensen, Scott B
• Application Number:
  US15/936,709
• Publication Number:
  US 20180213031A1
• Time in Patent Office: 567 Days
• Field of Search: None
• 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

Abstract

Provided are methods and systems for balancing servers based on a server load status. A method for balancing servers based on a server load status may commence with receiving, from a server of a plurality of servers, a service response to a service request. The service response may include a computing load of the server. The method may continue with receiving a next service request from a host. The method may further include determining, based on the computing load of the server, whether the server is available to process the next service request. The method may include selectively sending the next service request to the server based on the determination that the server is available to process the next service request.

Claims

1. A system for balancing servers based on a server load status, the system comprising:

a plurality of servers configured to process service requests; and

a service gateway comprising a processor and a computer readable storage medium having a computer readable program code embodied therewith, wherein the computer readable program code when executed by the processor causes the service gateway to;

receive, from a server of the plurality of servers, a service response to a service request, the service request including a Uniform Resource Locator (URL) of a plurality of URLs, the service response comprising a computing load of the server, each server of the plurality of servers being configured to act as a primary server for the URL, wherein the service gateway is pre-configured to;

automatically select, for each URL of the plurality of URLs, the primary server to process service requests associated with the each URL, and

select a secondary server to process the service requests associated with each URL for when the primary server is unavailable to process the service requests;

receive a next service request from a host, the next service request including the URL;

based on the URL and the computing load of the server, determine whether the server can currently act as the primary server for processing the next service request; and

based on the determination, selectively send the next service request to the server.

2. The system of claim 1, wherein the service gateway is further configured to:

receive the service request from the host, the service request including a first Uniform Resource Locator (URL) of a plurality of URLs, the first URL being associated with at least one server of the plurality of servers;

determine that the server is the primary server configured to process the first URL and a further server is the secondary server configured to process the first URL;

based on the determination that the server is the primary server, select the server to process the service request; and

send the service request to the server.

3. The system of claim 2, wherein each of the plurality of URLs is individually resolved to the primary server configured to process the URL and the secondary server configured to process the URL, each server of the plurality of servers being configured as one of primary servers and one of secondary servers for different URLs.

4. The system of claim 3, wherein the computing load of the server includes a server status of the server.

5. The system of claim 4, wherein the server status indicates one or more of the following:

the server is not busy when the server is available for serving as the primary server and is available for serving as the secondary server, the server is busy when the server is available for serving as the primary server and is unavailable for serving as the secondary server, and the server is very busy when the server is available for serving as the primary server with restrictions and is unavailable for serving as the secondary server.

6. The system of claim 4, wherein the determining by the service gateway whether the server is available to process the next service request comprises:

determining that the server status indicates the server is not busy;

determining that the next service request includes a second URL associated with the server as the primary server to process the second URL; and

in response to determination that the server is not busy and the next service request includes the second URL associated with the server as the primary server, selecting the server to process the next service request.

7. The system of claim 4, wherein the determination by the service gateway whether the server is available to process the next service request comprises:

determining that the server status indicates the server is busy;

determining that the next service request includes a second URL associated with the server as the primary server to process the second URL; and

in response to determination that the server is busy and the next service request includes the second URL associated with the server as the primary server, selecting the server to process the next service request.

8. The system of claim 4, wherein the determination by the service gateway whether the server is available to process the next service request comprises:

determining that the server status indicates the server is busy;

determining that the next service request includes a second URL associated with the server as the secondary server to process the second URL; and

in response to determination that the server is busy and the next service request includes the second URL associated with the server as the secondary server, selecting a different server to process the next service request.

9. The system of claim 4, wherein the determining by the service gateway whether the server is available to process the next service request comprises:

determining that the server status indicates the server is very busy;

determining that the next service request includes a second URL associated with the server as the primary server to process the second URL; and

in response to determination that the server is very busy and the next service request includes the second URL associated with the server as the primary server, configuring a timer for a duration; and

in response to an expiration of the timer, selecting the server to process the next service request.

10. The system of claim 1, wherein the service response is one of the following:

a Hypertext Transport Protocol response, an Extensible Markup Language document, a Session Initiation Protocol packet, and a File Transfer Protocol response.

11. A method for balancing servers based on a server load status, the method comprising:

receiving, by a service gateway, from a server of a plurality of servers, a service response to a service request, the service request including a Uniform Resource Locator (URL) of a plurality of URLs, the service response comprising a computing load of the server, each server of the plurality of servers being configured to act as a primary server for the URL, wherein the service gateway;

automatically selects, for each URL of the plurality of URLs, the primary server to process service requests associated with the each URL, and

selects a secondary server to process the service requests associated with each URL for when the primary server is unavailable to process the service requests;

receiving, by the service gateway, a next service request from a host, the next service request including the URL;

based on the URL and the computing load of the server, determining, by the service gateway, whether the server can currently act as the primary server for processing the next service request; and

based on the determination, selectively sending, by the service gateway, the next service request to the server.

12. The method of claim 11, further comprising:

receiving, by the service gateway, the service request from the host, the service request including a first Uniform Resource Locator (URL) of a plurality of URLs, the first URL being associated with at least one server of the plurality of servers;

determining that the server is the primary server configured to process the first URL and a further server is the secondary server configured to process the first URL;

based on the determination that the server is the primary server, selecting the server to process the service request; and

sending the service request to the server.

13. The method of claim 12, wherein each of the plurality of URLs is individually resolved to the primary server configured to process the URL and the secondary server is configured to process the URL, each server of the plurality of servers being configured as one of primary servers and one of secondary servers for different URLs.

14. The method of claim 13, wherein the computing load of the server includes a server status of the server.

15. The method of claim 14, wherein the server status indicates one or more of the following:

the server is not busy when the server is available for serving as the primary server and is available for serving as the secondary server, the server is busy when the server is available for serving as the primary server and is unavailable for serving as the secondary server, and the server is very busy when the server is available for serving as the primary server with restrictions and is unavailable for serving as the secondary server.

16. The method of claim 14, wherein the determining whether the server is available to process the next service request comprises:

determining, by the service gateway, that the server status indicates the server is not busy;

determining, by the service gateway, that the next service request includes a second URL associated with the server as the primary server to process the second URL; and

in response to determination that the server is not busy and the next service request includes the second URL associated with the server as the primary server, selecting, by the service gateway, the server to process the next service request.

17. The method of claim 14, wherein the determination whether the server is available to process the next service request comprises:

determining, by the service gateway, that the server status indicates the server is busy;

determining, by the service gateway, that the next service request includes a second URL associated with the server as the primary server to process the second URL; and

in response to determination that the server is busy and the next service request includes the second URL associated with the server as the primary server, selecting, by the service gateway, the server to process the next service request.

18. The method of claim 14, wherein the determining whether the server is available to process the next service request comprises:

determining, by the service gateway, that the server status indicates the server is busy;

determining, by the service gateway, that the next service request includes a second URL associated with the server as the secondary server to process the second URL; and

in response to determination that the server is busy and the next service request includes the second URL associated with the server as the secondary server, selecting, by the service gateway, a different server to process the next service request.

19. The method of claim 14, wherein the determining whether the server is available to process the next service request comprises:

determining, by the service gateway, that the server status indicates the server is very busy;

determining, by the service gateway, that the next service request includes a second URL associated with the server as the primary server to process the second URL; and

in response to determination that the server is very busy and the next service request includes the second URL associated with the server as the primary server, configuring, by the service gateway, a timer for a duration; and

in response to an expiration of the timer, selecting, by the service gateway, the server to process the next service request.

20. A system for balancing servers based on a server load status, the system comprising:

a plurality of servers configured to process service requests; and

a service gateway comprising a processor and a computer readable storage medium having a computer readable program code embodied therewith, wherein the computer readable program code, when executed by the processor causes the service gateway to;

receive a service request from the host, the service request including a first Uniform Resource Locator (URL) of a plurality of URLs, the first URL being associated with at least one server of a plurality of servers;

determine that a server of the plurality of servers is a primary server configured to process the first URL and a further server of the plurality of servers is a secondary server configured to process the first URL, wherein the service gateway is pre-configured to;

automatically select, for each URL of the plurality of URLs, the primary server to process service requests associated with the each URL, and

select the secondary server to process the service requests associated with each URL for when the primary server is unavailable to process the service requests;

based on the determination that the server is the primary server, select the server to process the service request;

send the service request to the server;

receive, from the server, a service response to the service request, the service request including URL, the service response comprising a computing load of the server, each server of the plurality of servers being configured to act as the primary server for the URL;

receive a next service request from a host, the next service request including the URL;

based on the URL and the computing load of the server, determine whether the server can currently act as the primary server for processing the next service request, wherein the determining whether the server is available to process the next service request comprises;

determining that the server status indicates the server is not busy;

determining that the next service request includes a second URL associated with the server as the primary server to process the second URL; and

in response to determining the server s not busy and the next service request includes the second URL associated with the server as the primary server, selecting the server to process the next service request; and

based on the selection, selectively send the next service request to the server.