Server health monitoring for traffic load balancer
A device may receive, from a load balancing device, configuration information that identifies a set of nodes for which a status is to be determined. The device may generate a data structure. The data structure may store information that identifies a status of the set of nodes. The device may transmit a status request to one or more nodes. The device may determine the status of the one or more nodes based on transmitting the status request. The device may update the data structure based on determining a change in status of the one or more nodes. The device may provide, to the load balancing device, information that identifies the change in status of the one or more nodes based on updating the data structure.
1. A device comprising:
one or more processors to:
identify configuration information that identifies a set of nodes for which a status is to be determined;
select a backup node management device based on the configuration information,
the backup node management device being selected from the set of nodes for which the status is to be determined,
the device being associated with a first Internet Protocol (IP) address within a range of IP addresses,
the backup node management device being associated with a second IP address within the range of IP addresses, and
the backup node management device being selected based on the second IP address being, within the range of IP addresses, a next sequential IP address after the first IP address within the range of IP addresses; and
provide the configuration information to the backup node management device to permit the backup node management device to function as the backup node management device.
2. The device of claim 1 , where the first IP address is a highest available IP address within the range of IP addresses.
3. The device of claim 1 , where the device is a load balancing device.
4. The device of claim 1 , where the one or more processors are further to:
detect a failure of a previously assigned primary node management device before selecting the backup node management device.
5. The device of claim 4 ,
where the one or more processors, when detecting the failure, are to:
detect the failure of the previously assigned primary node management device based on a dropped connection.
6. The device of claim 4 , where the failure includes an inability to determine or update status updates.
7. The device of claim 4 , where the one or more processors are further to:
determine a set of status checks status for the set of nodes after detecting the failure of the previously assigned primary node management device.
8. A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
identify configuration information that identifies a set of nodes for which a status is to be determined;
select a backup node management device based on the configuration information,
the backup node management device being selected from the set of nodes for which the status is to be determined,
a primary node management device being associated with a first Internet Protocol (IP) address within a range of IP addresses,
the backup node management device being associated with a second IP address within the range of IP addresses, and
the backup node management device being selected based on a position of the second IP address being, within the range of IP addresses, a next sequential IP address after the first IP address within the range of IP addresses; and
provide the configuration information to the backup node management device to permit the backup node management device to function as the backup node management device.
9. The non-transitory computer-readable medium of claim 8 , where the one or more processors are in a load balancing device.
10. The non-transitory computer-readable medium of claim 8 , where the instructions further comprise:
one or more instructions that, when executed by the one or more processors, cause the one or more processors to:
detect, before selecting the backup node management device, a failure of a previously assigned primary node management device.
11. The non-transitory computer-readable medium of claim 8 , where the instructions further comprise:
one or more instructions that, when executed by the one or more processors, cause the one or more processors to:
detect a failure of a previously assigned primary node management device, and
perform, after detecting the failure, a set of status checks for the set of nodes in place of the previously assigned primary node management device.
12. The non-transitory computer-readable medium of claim 8 , where the configuration information comprises the second IP address.
13. The non-transitory computer-readable medium of claim 8 , where the first IP address is a highest available IP address within the range of IP addresses.
14. The non-transitory computer-readable medium of claim 8 , where the instructions further comprise:
one or more instructions that, when executed by the one or more processors, cause the one or more processors to:
receive the configuration information from a load balancing device.
15. A method comprising:
identifying, by a device, configuration information that identifies a set of nodes for which a status is to be determined,
the configuration information including a range of Internet Protocol (IP) addresses associated with the set of nodes;
selecting, by the device and from the set of nodes, a backup node management device based on the configuration information,
the device being associated with a first IP address within the range of IP addresses,
the backup node management device being associated with a second IP address within the range of IP addresses, and
the backup node management device being selected based on the second IP address being, within the range of IP addresses, a next sequential IP address after the first IP address within the range of IP addresses; and
providing, by the device, the configuration information to the backup node management device to permit the backup node management device to function as the backup node management device.
16. The method of claim 15 , where the first IP address is a highest available IP address within the range of IP addresses.
17. The method of claim 15 , further comprising:
detecting a failure of a previously assigned primary node management device; and
determining a set of status checks of the set of nodes based on detecting the failure of the previously assigned primary node management device.
18. The method of claim 17 , where the failure includes an inability to determine the set of status checks.
19. The method of claim 15 , further comprising:
detecting, before selecting the backup node management device, a failure of a previously assigned primary node management device based on a dropped connection.
20. The method of claim 15 , where the configuration information comprises the second IP address.