Load balancing for IP failover

Patent metadata

Field	Value
Publication number	US-11128573-B2
Application number	US-201916658280-A
Country	US
Kind code	B2
Filing date	Oct 21, 2019
Priority date	Oct 20, 2018
Publication date	Sep 21, 2021
Grant date	Sep 21, 2021

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.

First claim

What is claimed is:

1. A method comprising:
identifying a backend address of a first node 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; and
routing the request to a primary network interface on the first node using the backend address, wherein 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.

2. The method of claim 1 , comprising:
transmitting health probes to a first port of the first node, for routing through the node management logical interface to a health probe process executing on the first node, based upon a health probe definition.

3. The method of claim 2 , wherein the transmitting health probes comprises:
transmitting the health probes at defined intervals based upon the health probe definition.

4. The method of claim 2 , 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.

5. The method of claim 4 , comprising:
redirecting requests to a second backend address of a second node based upon the load balancer rule specifying that requests having the frontend address are to be rerouted from being routed to the backend address to being routed to the second backend address based upon the first node encountering the issue, wherein the data logical interface and the destination data structure are migrated from the first node to the second node.

6. The method of claim 5 , comprising:
receiving an acknowledgement from the second node to a health probe based upon the second node listening to the first port upon the second node determining that the first node encountered the issue.

7. The method of claim 6 , wherein the load balancer is triggered to redirect the requests to the second backend address based upon receiving the acknowledgement from the second node.

8. The method of claim 1 , wherein a floating address option is enabled for routing requests to backend addresses while retaining the frontend address of the requests as the request destination corresponding to the destination data structure maintained by nodes to which the requests are routed by the load balancer.

9. The method of claim 1 , wherein the load balancer is hosted by a cloud service within which the first node is instantiated as a first virtual machine having a high availability partnership with a second node instantiated as a second virtual machine within the cloud service.

10. The method of claim 1 , wherein a single backend pool of backend addresses are maintained for nodes.

11. The method of claim 1 , wherein a plurality of backend pools of backend addresses are maintained for a plurality of nodes.

12. A non-transitory machine readable medium comprising instructions for performing a method, which when executed by a machine, causes the machine to:
identify a backend address of a first node 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; and
route the request to a primary network interface of the first node using the backend address, wherein 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.

13. The non-transitory machine readable medium of claim 12 , wherein the instructions cause the machine to:
transmit health probes to a first port of the first node, for routing through the primary network interface to a health probe process executing on the first node, based upon a health probe definition.

14. The non-transitory machine readable medium of claim 13 , wherein the instructions cause the machine to:
transmit the health probes at defined intervals based upon the health probe definition.

15. The non-transitory machine readable medium of claim 13 , 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.

16. The non-transitory machine readable medium of claim 15 , wherein the instructions cause the machine to:
redirect requests to a second backend address of a second node based upon the load balancer rule specifying that requests having the frontend address are to be rerouted from being routed to the backend address to being routed to the second backend address based upon the first node encountering the issue, wherein the loopback interface and the destination data structure are migrated from the first node to the second node.

17. The non-transitory machine readable medium of claim 16 , wherein the instructions cause the machine to:
receive an acknowledgement from the second node to a health probe based upon the second node listening to the first port upon the second node determining that the first node encountered the issue.

18. The non-transitory machine readable medium of claim 17 , wherein the load balancer is triggered to redirect the requests to the second backend address based upon receiving the acknowledgement from the second node.

19. 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:
identify a backend address of a first node 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; and
route the request to a primary network interface of the first node using the backend address, wherein 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.

20. The computing device of claim 19 , wherein the instructions cause the processor to:
redirect requests specifying the frontend address to a second backend address of a second node based upon a threshold number of failures to receive acknowledgements of health probes send to a port of the first node.

Assignees

• Netapp Inc

Inventors

• Busick Christopher
• Vinnakota Mohinish
• Silva James
• Rajaraman Rajesh

Classifications

• H04L41/40

  using virtualisation of network functions or resources, e.g. SDN or NFV entities · CPC title

• H04L41/0895

  Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements · CPC title

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• G06F13/4221 Primary

  being an input/output bus, e.g. ISA bus, EISA bus, PCI bus, SCSI bus · CPC title

• H04L47/29

  using a combination of thresholds · CPC title