---
title: "Discussion on \"The Load Balancer That Kept Choosing a Broken Server\" | Hashnode"
description: "Discussion on \"The Load Balancer That Kept Choosing a Broken Server\". Why least-connections load balancing can send more traffic to a failing server, and how health checks and outlier detection prevent it."
url: "https://hashnode.com/posts/load-balancer-keeps-choosing-broken-server/6af82de44569fbbba71094f6"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The Load Balancer That Kept Choosing a Broken Server](https://de-system-designs.hashnode.dev/load-balancer-keeps-choosing-broken-server?utm_source=hashnode&utm_medium=feed)

Why least-connections load balancing can send more traffic to a failing server, and how health checks and outlier detection prevent it.

Oct 23 · 17 min read · de-system-designs.hashnode.dev  
Read the article

## Written by

[srkhan2809](https://hashnode.com/@shahida-khan)

@shahida-khan · Dubai, UAE

  
[View profile](https://hashnode.com/@shahida-khan)

Lead Data Infrastructure Architect | Databricks, PySpark & Cloud DW

I am a Lead Data Infrastructure Architect with 13+ years of experience engineering high-throughput data platforms for fintech and consumer apps. I specialize in the Databricks Lakehouse ecosystem, PySpark, BigQuery, and Snowflake. I write about modern data architecture, cloud cost optimization (FinOps), declarative ELT pipelines, and scaling systems to process 100K+ events per second. When I'm not untangling complex legacy databases, I'm building zero-loss data quality frameworks.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.