Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RING_HASH lb policy doesn't adjust load balancing weights when upstream hosts become unhealthy #38525

Open
cxhiano opened this issue Feb 22, 2025 · 0 comments
Labels
bug triage Issue requires triage

Comments

@cxhiano
Copy link

cxhiano commented Feb 22, 2025

Title: RING_HASH lb policy doesn't adjust load balancing weights when upstream hosts become unhealthy

Description:

According to this doc, Envoy adjusts traffic weights based on overprovisioning_factor and upstream host health status. This does not seem to be the case when lb_policy is set to RING_HASH.

Repro steps:

Configure a cluster with lb_policy set to RING_HASH and a load_assignment with endpoints across at least 2 localities, traffic distribution across localities doesn't seem to change as some upstream hosts become unhealthy.

Config:

  clusters:
  - name: test_service
    lb_policy: RING_HASH
    common_lb_config:
      locality_weighted_lb_config: {}
      healthy_panic_threshold:
        value: 1
    load_assignment:
 ...

cc: @tonya11en

@cxhiano cxhiano added bug triage Issue requires triage labels Feb 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug triage Issue requires triage
Projects
None yet
Development

No branches or pull requests

1 participant