Managing TCP anycast requests

1. A method for managing traffic in a content delivery network (CDN), comprising:

monitoring, with a network device, a number of requests being processed by a plurality of servers in a first node in said CDN;

receiving a request at the network device in the first node, wherein the request is serviceable by at least one of the first node and a second node;

first determining, with the network device, whether the first node has capacity to service the request;

second determining which server amongst the plurality of servers in the first node will receive the request if the first node is determined to have the capacity to service the request; and

redirecting, with the network device, the request to the second node if the first node is determined not to have a capacity to service the request as decided in the first determination,

wherein the first node and the second node share a same anycast IP address, wherein said second determination is performed by the network device.

2. The method for managing traffic as recited in claim 1 , wherein said network device is a server/router configured to determine whether the first node has the capacity to service the request based on a number of requests being processed by the first node.

3. The method for managing traffic as recited in claim 2 , wherein the server/router determines that the first node has the capacity to service the request if the number of requests being processed by the first node is less than a prescribed threshold number.

4. The method for managing traffic as recited in claim 1 , wherein

the network device comprises a server/router,

the request is received at the server/router,

the request is routed from the server/router to a load balancer within the first node,

the request is transmitted by the load balancer to the determined server to service the request, and

the determined server is a server determined by the load balancer to have capacity to service the request.

5. The method for managing traffic as recited in claim 1 , wherein the one server generates a response and transmits the generated response to a device that issued the request.

6. The method for managing traffic as recited in claim 1 , wherein

the network device comprises a router/load balancer device,

the request is received at the router/load balancer device,

the request is transmitted to the determined server to service the request by the router/load balancer device; and

the determined server is a server determined by the router/load balancer device to have capacity to the service the request.

7. The method for managing traffic as recited in claim 1 , wherein

said request is a TCP anycast request.

8. The method for managing traffic as recited in claim 1 , wherein the redirecting of the request to the second node is via a virtual tunnel.

9. The method for managing traffic as recited in claim 1 , wherein a unicast address of the second node is used when redirecting the request to the second node.

10. The method for managing traffic as recited in claim 1 , wherein the second node is configured to generate and send a response to an end user after the request is redirected to the second node.

11. A system for managing traffic in a content delivery network (CDN), comprising:

a network device at a first node of a plurality of nodes in the CDN, said network device configured to:

monitor a number of requests being processed by a plurality of servers in the first node;

receive a request, wherein the request is serviceable by at least one of the first node and a second node of the plurality of nodes;

first determine whether one of the plurality of servers in the first node has capacity to service the request;

second determine which server amongst the plurality of servers in the first node will receive the request if the first node is determined to have the capacity to service the request; and

redirect the request to the second node if the first node does not to have a capacity to service the request as decided in the first determination,

wherein the first node and the second node share a same anycast IP address, wherein said second determination is performed by the network device.

12. The system for managing traffic as recited in claim 11 , wherein said network device is a server/router configured to determine whether the first node has the capacity to service the request based on a number of requests being processed by the first node.

13. The system for managing traffic as recited in claim 12 , wherein the server/router determines that the first node has the capacity to service the request if the number of requests being processed by the first node is less than a prescribed threshold number.

14. The system for managing traffic as recited in claim 11 , wherein

the network device comprises a server/router,

the server/router is configured to receive the request and route the request to a load balancer within the first node,

the load balancer is configured to transmit the request to the determined server to service the request, and

the determined server is a server determined by the load balancer to have capacity to service the request.

15. The system for managing traffic as recited in claim 11 , wherein the one server is configured to generate a response and transmit the generated response to a device that issued the request.

16. The system for managing traffic as recited in claim 11 , wherein

the network device comprises a router/load balancer device,

the router/load balancer device is configured to receive the request and transmit the request to the determined server to service the request; and

the determined server is a server determined by the router/load balancer device to have capacity to service the request.

17. The system for managing traffic as recited in claim 11 , wherein

said request is a TCP anycast request.

18. The system for managing traffic as recited in claim 11 , further comprising:

a virtual tunnel,

wherein the redirecting of the request to the second node is via the virtual tunnel.

19. The system for managing traffic as recited in claim 11 , wherein a unicast address of the second node is used when redirecting the request to the second node.