envoyproxy/envoy

Return gRPC error status when max_stream_duration is reached for gRPC requests

Open

#13,925 opened on Nov 6, 2020

View on GitHub
 (16 comments) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
area/grpchelp wanted

Repository metrics

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

Description

Title: Return gRPC error status when max_stream_duration is reached for gRPC requests

Description: When max_stream_duration is set in the listener_config or cluster_config, it would be helpful to return an gRPC error status when the duration is reached, so that the client can get a better signal and choose to handle it gracefully.

Contributor guide

Research direction
Investigate the code in envoy that handles max stream duration and determine where to add gRPC error status when the duration is exceeded. Look for relevant filters or connection manager code.
Tech stack
grpc
Domain
backendapinetworking
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.
Half day
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++gRPCEnvoy internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30