envoyproxy/envoy

Load balance long-lived connections upon auto scale-out or scale-in of Envoy

Open

#15,283 opened on Mar 3, 2021

View on GitHub
 (13 comments) (4 reactions) (0 assignees)C++ (5,373 forks)batch import
area/adminhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Consider a scenario where there is auto scale-out of Envoy. In such a situation, I would actually like to drain few connections from an old instance and transfer that load to the newly scaled-out instance. Currently, I cannot find a way to drain a certain amount of connections an Envoy instance handles.

Would it be possible to have some sort of configuration where we could set the percentage of connections to drain based on certain parameters like number of connections per envoy instance or the total number of connections ?

Contributor guide

Research direction
Investigate Envoy's existing connection draining and cluster scaling mechanisms. Propose a design for draining a percentage of connections based on per instance connection counts or total connections.
Tech stack
cpp
Domain
backendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
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.
Mostly clear
Prerequisites
C++Envoy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20