ThreeMammals/Ocelot

How to avoid calling down service in load balancer option

Open

#1,041 opened on Oct 17, 2019

View on GitHub
 (14 comments) (0 reactions) (0 assignees)C# (1,617 forks)batch import
Health CheckLoad BalancerQoSacceptedbughelp wantedhighmedium effort

Repository metrics

Stars
 (8,137 stars)
PR merge metrics
 (Avg merge 44d 17h) (6 merged PRs in 30d)

Description

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:

Contributor guide

Research direction
Implement health checks for downstream services in the load balancer to avoid routing to down instances. Look at Ocelot's load balancer pipeline and add a health check step before routing.
Tech stack
csharp
Domain
api
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#load balancing concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70