ThreeMammals/Ocelot

How to avoid calling down service in load balancer option

Open

#1,041 建立於 2019年10月17日

在 GitHub 查看
 (14 留言) (0 反應) (0 負責人)C# (8,137 star) (1,617 fork)batch import
Health CheckLoad BalancerQoSacceptedbughelp wantedhighmedium effort

描述

Expected Behavior / New Feature

Load balancer should able to recognize the down service and stop calling service or up the service.

Actual Behavior / Motivation for New Feature

Load balancer is calling the service although the service is down and returning 500 internal server on every call.

Steps to Reproduce the Problem

  1. Created two instance of the same module and run on different port.
  2. Added load balance option for those two service instance of type RoundRobin.
  3. Kill the second service and now Ocelot still redirect to down service.

Specifications

  • Version: 13.5.2
  • Platform: Windows 10
  • Subsystem:

貢獻者指南

技術棧
csharp
領域
backendapiperformance
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
needs maintainer response
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
C#load balancing concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
This feature request asks the Ocelot API Gateway to avoid routing to a down service. The solution likely involves implementing health checks that periodically probe backends and update the load balancer's state. Begin by examining the existing load balancer implementation in Ocelot, particularly the RoundRobin class and how it selects downstream services. Then review any existing health check middleware or discuss with maintainers on the issue thread to clarify desired design (e.g., passive vs active health checks). Suggested files to investigate: src/Ocelot/LoadBalancer/LoadBalancers/ and related tests.
How to avoid calling down service in load balancer option · ThreeMammals/Ocelot#1041 | Good First Issue