ACTIVE APPLICATION RESPONSE DELAY TIME

• US 20150281104A1
• Filed: 03/31/2014
• Published: 10/01/2015
• Est. Priority Date: 03/31/2014
• Status: Active Grant

• Current Assignee: A10 Networks Incorporated
• Original Assignee: A10 Networks Incorporated
• Inventors: Golshan, Ali, Yang, Yang, Grimm, Martin
• Granted Patent: US 9,942,162 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/283 in response to processing delays, e.g. caused by jitter or round trip time [RTT]

Abstract

Provided are methods and systems for load balancing client requests between sites associated with a domain name. A method comprises determining a first active response delay time between a local Domain Name System (DNS) server and a first site. The method further comprises determining a first application response delay time between the first site and one or more first servers associated with the first site. According to the method, the first active response delay time and the first application response delay time are compounded to produce a first compounded response delay time. The method further comprises determining a second active response delay time and a second application response delay for a second site to produce a second compounded response delay time. The first compounded response delay time and the second compounded response delay time are compared to perform load balancing between the first site and the second site.

Claims

1. A method for load balancing client requests between sites associated with a domain name, the method comprising:

determining a first active response delay time between a local Domain Name System (DNS) server and a first site;

determining a first application response delay time between the first site and one or more first servers associated with the first site;

compounding the first active response delay time and the first application response delay time to produce a first compounded response delay time;

determining a second active response delay time between the local DNS server and a second site;

determining a second application response delay time between the second site and one or more second servers associated with the second site;

compounding the second active response delay time and the second application response delay time to produce a second compounded response delay time;

comparing the first compounded response delay time and the second compounded response delay time; and

based on the comparison, performing load balancing between the first site and the second site.

2. The method of claim 1, wherein determining the first active response delay time includes:

sending a request from a site load balancer associated with the first site to the local DNS server, the request being associated with a first time;

receiving a response from the local DNS server, the response being associated a second time; and

determining a time difference between the first time and the second time; and

wherein determining the second active response delay time includes;

sending a request from a site load balancer associated with the second site to the local DNS server, the request being associated with a first time;

receiving a response from the local DNS server, the response being associated with a second time; and

determining a time difference between the first time and the second time.

3. The method of claim 1, wherein determining the first application response delay time includes:

sending a request from a site load balancer associated with the first site to the one or more servers associated with the first site, the request being associated with a first time;

receiving a response from the one or more servers, the response being associated with a second time; and

determining a time difference between the first time and the second time; and

wherein determining the second application response delay time includes;

sending a request from a site load balancer associated with the second site to the one or more servers associated with the second site, the request being associated with a first time;

receiving a response from the one or more servers, the response being associated with a second time; and

determining a time difference between the first time and the second time.

4. The method of claim 1, further comprising reporting results of the comparison between the first compounded response delay time and the second compounded response delay time to a global site load balancer, wherein the global site load balancer coordinates the load balancing between the first site and the second site.

5. The method of claim 1, further comprising routing a client request to the site with a lowest compounded response delay time.

6. The method of claim 1, further comprising:

storing the first active response delay time and the first application response delay time into a database; and

storing the second active response delay time and the second application response delay time into the database.

7. The method of claim 1, further comprising:

retrieving the first application response delay time and first active response delay time from a database; and

retrieving the second application response delay time and second active response delay time from the database.

8. The method of claim 1, further comprising:

determining a geographical location for the local DNS server;

determining one or more sites from a plurality of sites based on a client request;

determining a geographical location for the one or more determined sites;

determining that the geographic location for the local DNS server matches the geographic location for the one or more determined sites;

selecting the first site from the one or more determined sites, wherein a geographic location of the first site matches the geographic location for the local DNS server; and

selecting the second site from the one or more determined sites, wherein a geographic location of the second site matches the geographic location for the local DNS server.

9. The method of claim 8, further comprising composing a table of responses, the table of responses including an IP address associated with the local DNS server, an IP address associated with the first site, the first active response delay time, an IP address associated with the second site, and the second active response delay time.

10. A system for load balancing client requests between sites associated with a domain name, the system comprising:

one or more processors operable to;

determine a first active response delay time between a local Domain Name System (DNS) server and a first site;

determine a first application response delay time between the first site and one or more first servers associated with the first site;

compound the first active response delay time and the first application response delay time to produce a first compounded response delay time;

determine a second active response delay time between the local DNS server and a second site;

determine a second application response delay time between the second site and one or more second servers associated with the second site;

compound the second active response delay time and the second application response delay time to produce a second compounded response delay time;

compare the first compounded response delay time and the second compounded response delay time; and

based on the comparison, perform load balancing between the first site and the second site.

11. The system of claim 10, wherein the determining the first active response delay time includes:

sending a request from a site load balancer associated with the first site to the local DNS server, the request being associated with a first time;

receiving a response from the local DNS server, the response being associated a second time;

determining a time difference between the first time and the second time; and

wherein determining the second active response delay time includes;

sending a request from a site load balancer associated with the second site to the local DNS server, the request being associated with a first time;

receiving a response from the local DNS server, the response being associated a second time; and

determining a time difference between the first time and the second time.

12. The system of claim 10, wherein the determining the first application response delay time includes:

sending a request from a site load balancer associated with the first site to the one or more servers associated with the first site, the request being associated with a first time;

receiving a response from the one or more servers, the response being associated with a second time;

determining a time difference between the first time and the second time; and

wherein determining the second application response delay time includes;

sending a request from a site load balancer associated with the second site to the one or more servers associated with the second site, the request being associated with a first time;

receiving a response from the one or more servers, the response being associated with a second time; and

determining a time difference between the first time and the second time.

13. The system of claim 10, wherein the one or more processors coordinate the load balancing between the first site and the second site based on results of the comparison between the first compounded response delay time and the second compounded response delay time.

14. The system of claim 10, wherein the one or more processors are further operable to:

route a client request to the site with a lowest compounded response delay time.

15. The system of claim 10, wherein the one or more processors are further operable to:

store the first active response delay time and the first application response delay time into a database; and

store the second active response delay time and the application response delay time into the database.

16. The system of claim 10, wherein the one or more processors are further operable to:

retrieve the first application response delay time and the first active response delay time from a database; and

retrieve the second application response delay time and the second active response delay time from the database.

17. The system of claim 10, wherein the one or more processors are further operable to:

determine a geographical location for the local DNS server;

determine one or more sites from a plurality of sites based on a client request;

determine a geographical location for the one or more determined sites;

determine that the geographic location for the local DNS server matches the geographic location for the one or more determined sites;

select the first site from the one or more determined sites, wherein a geographic location of the first site matches the geographic location for the local DNS server; and

select the second site from the one or more determined sites, wherein a geographic location of the second site matches the geographic location for the local DNS server.

18. The method of claim 10, wherein the one or more processors are further operable to:

compose a table of responses, the table of responses including an IP address associated with the local DNS server, an IP address associated with the first site, the first active response delay time, an IP address associated with the second site, and the second active response delay time.

19. The system of claim 10, further comprising a database operable to store data associated with the first application response delay time, the first active response delay time, the second application response delay time, the second active response delay time, the first compounded response delay time, and the second compounded response delay time.

20. A non-transitory processor-readable medium having instructions stored thereon, which when executed by one or more processors, cause the one or more processors to implement a method for load balancing client requests between sites associated with a domain name, the method comprising:

determining a first active response delay time between a local Domain Name System (DNS) server and a first site;

determining a first application response delay time between the first site and one or more first servers associated with the first site;

compounding the first active response delay time and the first application response delay time to produce a first compounded response delay time;

determining a second active response delay time between the local DNS server and a second site;

determining a second application response delay time between the second site and one or more second servers associated with the second site;

compounding the second active response delay time and the second application response delay time to produce a second compounded response delay time;

comparing the first compounded response delay time and the second compounded response delay time; and

based on the comparison, performing load balancing between the first site and the second site.