Dynamically adjusting load balancing

• US 9,774,537 B2
• Filed: 12/01/2014
• Issued: 09/26/2017
• Est. Priority Date: 09/30/2014
• Status: Active Grant

• Current Assignee: Nicira Incorporated (Broadcom, Inc.)
• Original Assignee: Nicira Incorporated (Broadcom, Inc.)
• Inventors: Jain, Jayant, Sengupta, Anirban, Parthasarathy, Mohan, Sequeira, Allwyn, Maskalik, Serge, Lund, Rick
• Primary Examiner(s): Donabed, Ninos
• Application Number:
  US14/557,295
• Publication Number:
  US 20160094643A1
• Time in Patent Office: 1,030 Days
• Field of Search: None
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 2101/622 Layer-2 addresses, e.g. medium access control [MAC] addresses
• CPC Class Codes: H04L 45/24 Multipath
• CPC Class Codes: H04L 45/44 Distributed routing
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 61/2521 Translation architectures other than single NAT servers
• CPC Class Codes: H04L 61/5069 for group communication, multicast communication or broadcast communication
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1017 based on a round robin mechanism
• CPC Class Codes: H04L 67/1025 Dynamic adaptation of the criteria on which the server selection is based
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer

Abstract

Some embodiments provide a novel method for load balancing data messages that are sent by a source compute node (SCN) to one or more different groups of destination compute nodes (DCNs). In some embodiments, the method deploys a load balancer in the source compute node'"'"'s egress datapath. This load balancer receives each data message sent from the source compute node, and determines whether the data message is addressed to one of the DCN groups for which the load balancer spreads the data traffic to balance the load across (e.g., data traffic directed to) the DCNs in the group. When the received data message is not addressed to one of the load balanced DCN groups, the load balancer forwards the received data message to its addressed destination. On the other hand, when the received data message is addressed to one of load balancer'"'"'s DCN groups, the load balancer identifies a DCN in the addressed DCN group that should receive the data message, and directs the data message to the identified DCN. To direct the data message to the identified DCN, the load balancer in some embodiments changes the destination address (e.g., the destination IP address, destination port, destination MAC address, etc.) in the data message from the address of the identified DCN group to the address (e.g., the destination IP address) of the identified DCN.

Claims

1. A non-transitory machine readable medium storing sets of instructions for performing load balancing operations on a particular host computer on which at least one particular source compute node (SCN) executes, the sets of instructions comprising instructions for:

based on a set of load balancing criteria, distributing data messages sent by the particular SCN among the destination compute nodes (DCNs) of a DCN group,

sending, to a set of controllers, message traffic statistics relating to data messages that are distributed among the DCNs of the DCN group;

receiving, from the set of controllers, data that identifies at least one DCN that has been removed from the DCN group;

receiving, from the set of controllers, a set of adjusted load balancing criteria that the set of controllers calculates by (1) collecting message traffic statistics from a plurality of host computers performing load balancing operations for data messages sent by SCNs executing on the host computers, (2) aggregating the collected message traffic statistics, and (3) computing the adjusted load balancing criteria from the aggregated collected message traffic statistics;

based on the received set of adjusted load balancing criteria, adjusting the distribution of the data message flows from the particular SCN among the DCNs of the DCN group; and

directing, after receiving the updated membership data, all new data message flows to a subset of DCNs in the DCN group that does not include the removed DCN.

2. The non-transitory machine readable medium of claim 1, wherein the aggregated message traffic statistics expresses the data message traffic load on each DCN in the DCN group.

3. The non-transitory machine readable medium of claim 1, wherein the aggregated message traffic statistics expresses either the number of flows, packets or bytes directed to each DCN.

4. The non-transitory machine readable medium of claim 1, wherein the aggregated message traffic statistics expresses a relative congestion percentage of each DCN.

5. The non-transitory machine readable medium of claim 1 further comprising a set of instructions for receiving at the particular host computer an initial set of load balancing criteria as part of an initial configuration for the load balancing operations.

6. The non-transitory machine readable medium of claim 5, wherein the load balancing criteria specifies numerical values that affect how the data messages are distributed among the DCNs.

7. The non-transitory machine readable medium of claim 6, wherein the numerical values include one weight value for each DCN, wherein the set of instructions for distributing the data messages comprises a set of instructions for performing based on the weight values, a weighted round robin selection of the DCNs for new data message flows.

8. The non-transitory machine readable medium of claim 1, wherein the received load balancing criteria set specifies a weight value for each DCN.

9. The non-transitory machine readable medium of claim 1, the sets of instructions further comprising sets of instructions for:

receiving data that identifies at least one new DCN that has been added to the DCN group; and

directing a portion of new data message flows to the newly added DCN.

10. The non-transitory machine readable medium of claim 1, wherein the removed DCN is a DCN that has been removed from the DCN group due to an operational failure at the DCN, and

the sets of instructions further comprises a set of instructions for redirecting message data flows that were previously being directed to the removed DCN to other DCNs in the group.

11. The non-transitory machine readable medium of claim 1, the sets of instructions further comprising sets of instructions for:

intercepting each data message from the SCN,

determining whether the data message is addressed to the DCN group, and

directing the data message to one of the DCNs in the DCN group when the data message is addressed to the DCN group.

12. The non-transitory machine readable medium of claim 11, wherein the set of instructions for directing the data message comprises a set of instructions for directing at least two different data messages that are part of two different data message flows to two different DCNs of the DCN group.

13. The non-transitory machine readable medium of claim 11, wherein the set of instructions for directing the data message comprises a set of instructions for supplying the data message to a software forwarding element (SFE) that executes on the load balancer'"'"'s host computing device, for the SFE to forward the data message to an addressed destination.

14. A method for performing load balancing operations on a particular host computer on which at least one particular source compute node (SCN) executes, the method comprising:

based on a set of load balancing criteria, distributing data messages sent by the particular SCN among the destination compute nodes (DCNs) of a DCN group,

sending, to a set of controllers, message traffic statistics relating to data messages that are distributed among the DCNs of the DCN group;

from the set of controllers, receiving a set of adjusted load balancing criteria that the set of controllers calculates by (1) collecting message traffic statistics from a plurality of host computers performing load balancing operations for data messages sent by SCNs executing on the host computers, (2) aggregating the collected message traffic statistics, and (3) computing the adjusted load balancing criteria from the aggregated collected message traffic statistics; and

from the set of controllers, receiving data that identifies at least one DCN that has been removed from the DCN group;

based on the received set of adjusted load balancing criteria, adjusting the distribution of the data message flows from the particular SCN among the DCNs of the DCN group; and

directing, after receiving the updated membership data, all new data message flows to a subset of DCNs in the DCN group that does not include the removed DCN.

15. The method of claim 14, wherein the aggregated message traffic statistics expresses the data message traffic load on each DCN in the DCN group.