load balancer health check
A test a load balancer runs against each backend, such as opening a port or requesting a URL, to decide whether it should receive traffic.
In more detail
A shallow check, such as a TCP connect, proves only that a port accepts connections. An application check, such as an HTTP request that must return the expected status and content, proves much more. Match the check's layer to the failures users would see, or a broken backend stays in the pool.
Example
tcp=pass http=fail backend=drain action=remove shows a backend that accepts connections but fails the application check.Related terms
- load balancing — Spreading requests or connections across several backend servers so no single one is overloaded and failed ones can be avoided.
- backend pool — The set of servers a load balancer can send traffic to, each marked eligible or not by health checks.
- HTTP status code — The three-digit number at the start of a response, such as 200 or 404, that says how the server handled the request.
- transport layer — The layer that carries data between programs on two machines, identified by port numbers, using TCP or UDP.
- application layer — The top layer, where protocols such as HTTP, DNS and SSH give the bytes meaning as requests, answers and commands.
Taught in
- Load Balancing: Algorithms, Health Checks And Layers — Linux Fundamentals & Systems Administration