System and method to balance servers based on server load status

• US 9,961,135 B2
• Filed: 12/01/2015
• Issued: 05/01/2018
• 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:
  US14/956,230
• Publication Number:
  US 20160088074A1
• Time in Patent Office: 882 Days
• 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

A method, system, and computer program product for balancing servers based on server load status, include: receiving from a server a service response to a service request, the service response including a result from a processing of the service request and a server status indicating a computing load status of the server; obtaining the server status from the service response; receiving a next service request from a host, the next service request comprising a Uniform Resource Locator (URL); determining that the server is configured to process the URL; determining whether the server status indicates that the server is available to process the next service request; and in response to determining that the server status indicates that the server is available to process the next service request, sending the next service request to the server.

Claims

1. A method for balancing servers by a service gateway comprising:

receiving, by the service gateway, a first service request from a host, the service request including a first Uniform Resource Locator (URL) associated with at least one server of a plurality of servers, each URL of URLs being individually resolved to a primary server configured to process the URL and a 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 such that any given server resolves as a primary server for a first given URL and resolves as a secondary server for a second given URL, the service gateway being configured to automatically select, for each URL of the URLs, the primary server configured to process the URL for processing service requests associated with the URL;

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

based on the determining that the first server is the primary server, selecting the primary server associated with the first URL to process the first service request;

receiving a service response from the primary server, the service response including a server status indicating a computing load status of the primary server;

obtaining the server status from the service response; and

using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server.

2. The method of claim 1, wherein the using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server comprises:

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

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

in response to determining the first server is not busy and the second service request includes a second URL associated with the first server as the primary server, selecting the primary first server to process the second service request.

3. The method of claim 1, wherein the using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server comprises:

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

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

in response to determining the first server is busy and the second service request includes a second URL associated with the first server as the primary server, selecting the first server to process the second service request.

4. The method of claim 1, wherein the using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server comprises:

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

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

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

5. The method of claim 1, wherein the using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server comprises:

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

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

in response to determining the first server is very busy and the second service request includes a second URL associated with the first server, configuring a timer for a duration; and

in response to the expiration of the timer, selecting the first server to process the second service request.

6. The method of claim 1, wherein the obtaining the server status from the service response comprises:

locating a server status in the service response;

removing the server status from the service response; and

sending a modified service response to the host.

7. The method of claim 1, wherein the service response is at least one of an HTTP response and an XML document.

8. The method of claim 1 wherein the service response is at least one of an SIP packet and an FTP response.

9. A non-transitory computer readable storage medium having embodied thereon instructions, the instructions being executable by a processor to perform a method for balancing servers, the method comprising:

receiving, by the service gateway, a first service request from a host, the service request including a first Uniform Resource Locator (URL) associated with at least one server of a plurality of servers, each URL of URLs being individually resolved to a primary server configured to process the URL and a 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 such that any given server resolves as a primary server for a first given URL and resolves as a secondary server for a second given URL, the service gateway being configured to automatically select, for each URL of the URLs, the primary server configured to process the URL for processing service requests associated with the URL;

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

based on the determining that the first server is the primary server, selecting the primary server associated with the first URL to process the first service request;

receiving a service response from the primary server, the service response including a server status indicating a computing load status of the primary server;

obtaining the server status from the service response; and

using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server.

10. The non-transitory computer readable storage medium of claim 9, wherein the using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server comprises:

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

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

in response to determining the first server is not busy and the second service request includes a second URL associated with the first server as the primary server, selecting the primary first server to process the second service request.

11. The non-transitory computer readable storage medium of claim 9, wherein the using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server comprises:

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

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

in response to determining the first server is busy and the second service request includes a second URL associated with the first server as the primary server, selecting the first server to process the second service request.

12. The non-transitory computer readable storage medium of claim 9, wherein the using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server comprises:

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

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

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

13. The non-transitory computer readable storage medium of claim 9, wherein the using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server comprises:

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

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

in response to determining the first server is very busy and the second service request includes a second URL associated with the first server, configuring a timer for a duration; and

in response to the expiration of the timer, selecting the first server to process the second service request.

14. The non-transitory computer readable storage medium of claim 9, wherein the obtaining the server status from the service response comprises:

locating a server status in the service response;

removing the server status from the service response; and

sending a modified service response to the host.

15. A system comprising:

a processor; and

a memory coupled to the processor, the memory storing instructions, the instructions being executable by the processor to perform a method for balancing servers, the method comprising;

receiving, by the service gateway, a first service request from a host, the service request including a first Uniform Resource Locator (URL) associated with at least one server of a plurality of servers, each URL of URLs being individually resolved to a primary server configured to process the URL and a 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 such that any given server resolves as a primary server for a first given URL and resolves as a secondary server for a second given URL, the service gateway being configured to automatically select, for each URL of the URLs, the primary server configured to process the URL for processing service requests associated with the URL;

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

based on the determining that the first server is the primary server, selecting the primary server associated with the first URL to process the first service request;

receiving a service response from the primary server, the service response including a server status indicating a computing load status of the primary server;

obtaining the server status from the service response; and

using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server.

16. The system of claim 15, wherein the using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server comprises:

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

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

in response to determining the first server is not busy and the second service request includes a second URL associated with the first server as the primary server, selecting the primary first server to process the second service request.

17. The system of claim 15, wherein the using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server comprises:

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

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

in response to determining the first server is busy and the second service request includes a second URL associated with the first server as the primary server, selecting the first server to process the second service request.

18. The system of claim 15, wherein the using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server comprises:

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

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

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

19. The system of claim 15, wherein the using the server status from the service response to determine whether the first server is available to process a second service request including a URL associated with at least one server comprises:

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

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

in response to determining the first server is very busy and the second service request includes a second URL associated with the first server, configuring a timer for a duration; and

in response to the expiration of the timer, selecting the first server to process the second service request.

20. The system of claim 15, wherein the obtaining the server status from the service response comprises:

locating a server status in the service response;

removing the server status from the service response; and

sending a modified service response to the host.