envoyproxy/envoy

Envoy ALS message rotation on multiple streams

Open

#17,331 opened on Jul 14, 2021

View on GitHub
 (23 comments) (1 reaction) (1 assignee)C++ (5,373 forks)batch import
area/access_logarea/grpcenhancementhelp wanted

Repository metrics

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

Description

This issue proposes to introduce connection re-establishment in the Envoy ALS gRPC client. In the current implementation, the connection between Envoy and the receiver survives for so long that scaling out the receiver does not make sense; in order to perform load balancing of the Envoy ALS receiver, the Async gRPC client of Envoy needs to re-establish the connection at regular intervals or at some To load balance the Envoy ALS receiver, the Async gRPC client of Envoy needs to re-establish the connection at regular intervals or according to some other criteria. When no connection is established, logs are watermark buffered and flushed as needed.

cc. @lizan

Contributor guide

Research direction
Investigate the current Envoy ALS gRPC client implementation, focusing on how the async gRPC client manages streams and connections. Understand the connection lifecycle and identify points where reconnection could be introduced. Review existing load balancing mechanisms in Envoy's gRPC framework.
Tech stack
grpc
Domain
networking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 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.
Clear
Prerequisites
gRPCC++Envoy internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30