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.