Load balancing for ip failover

Abstract

Techniques are provided for load balancing for IP failover. A backend address of a first node is identified as a routing destination to which a request is to be routed by a load balancer based upon a load balancer rule mapping a frontend address, specified by the request as a request destination, to the backend address of the first node. The request is routed to a primary network interface of the first node using the backend address. The first node has a loopback interface with an address matching the frontend address for routing the request to a destination data structure based upon the request maintaining the frontend address as the request destination. Health probes are used by the load balancer for detecting a failure of the first node in order to failover to routing requests to a second backend address of a second node.

What is claimed is: 
     
         1 . A method comprising:
 generating a health probe based upon a health probe definition;   identifying a health probe process executing on a first node; and   transmitting the health probe to a port of the first node for routing through a node management logical interface to the health probe process executing on the first node.   
     
     
         2 . The method of  claim 1 , comprising:
 generating and transmitting health probes at defined intervals based upon the health probe definition.   
     
     
         3 . The method of  claim 1 , comprising:
 determining that the first node has encountered an issue based upon a failure to receive acknowledgement of a threshold number of health probes back from the health probe process.   
     
     
         4 . The method of  claim 3 , comprising:
 redirecting requests to a second backend address of a second node based upon a load balancer rule.   
     
     
         5 . The method of  claim 4 , wherein the load balancer rule specifies that requests having a frontend address are to be rerouted from being routed to a first backend address of the first node to being routed to the second backend address based upon the first node encountering the issue. 
     
     
         6 . The method of  claim 5 , comprising:
 migrating a data logical interface and a destination data structure from the first node to the second node.   
     
     
         7 . The method of  claim 4 , comprising:
 receiving an acknowledgement from the second node to the health probe based upon the second node listening to the port upon the second node determining that the first node encountered the issue.   
     
     
         8 . The method of  claim 5 , wherein the load balancer is triggered to redirect the requests to the second backend address based upon receiving the acknowledgement from the second node. 
     
     
         9 . The method of  claim 1 , comprising:
 generating one or more nodes for processing requests and responding to health probes.   
     
     
         10 . The method of  claim 9 , wherein the one or more nodes may comprise virtual machines comprising health probe processes. 
     
     
         11 . The method of  claim 1 , comprising:
 in response to the first node failing, redirecting requests to a second node.   
     
     
         12 . A non-transitory machine readable medium comprising instructions for performing a method, which when executed by a machine, causes the machine to:
 generate a health probe based upon a health probe definition;   identify a health probe process executing on a first node; and   transmit the health probe to a port of the first node for routing through a node management logical interface to the health probe process executing on the first node.   
     
     
         13 . The non-transitory machine readable medium of  claim 12 , wherein the instructions cause the machine to:
 generate and transmitting health probes at defined intervals based upon the health probe definition.   
     
     
         14 . The non-transitory machine readable medium of  claim 12 , wherein the instructions cause the machine to:
 determine that the first node has encountered an issue based upon a failure to receive acknowledgement of a threshold number of health probes back from the health probe process.   
     
     
         15 . The non-transitory machine readable medium of  claim 14 , wherein the instructions cause the machine to:
 redirect requests to a second backend address of a second node based upon a load balancer rule.   
     
     
         16 . The non-transitory machine readable medium of  claim 15 , wherein the load balancer rule specifies that requests having a frontend address are to be rerouted from being routed to a first backend address of the first node to being routed to the second backend address based upon the first node encountering the issue. 
     
     
         17 . A computing device comprising:
 a memory comprising instructions; and   a processor coupled to the memory, the processor configured to execute the instructions to cause the processor to:
 generate a health probe based upon a health probe definition; 
 identify a health probe process executing on a first node; and 
 transmit the health probe to a port of the first node for routing through a node management logical interface to the health probe process executing on the first node. 
   
     
     
         18 . The computing device of  claim 17 , wherein the instructions cause the processor to:
 generate and transmitting health probes at defined intervals based upon the health probe definition.   
     
     
         19 . The computing device of  claim 17 , wherein the instructions cause the processor to:
 determine that the first node has encountered an issue based upon a failure to receive acknowledgement of a threshold number of health probes back from the health probe process.   
     
     
         20 . The computing device of  claim 19 , wherein the instructions cause the processor to:
 redirect requests to a second backend address of a second node based upon a load balancer rule.