envoyproxy/envoy

Make sure retries work well for mobile

Open

#16,310 opened on May 4, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
cronvoy-alphaenhancementhelp wanted

Repository metrics

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

Description

The mobile stack (+DFP and ideally Envoy in general) needs to retry requests that were failed for non-fatal reasons (HTTP GOAWAY, QUIC 0-RTT rejection, etc.)

Contributor guide

Research direction
Investigate the existing retry mechanisms in Envoy (source/common/http/async client impl.cc, source/common/http/conn manager impl.cc) and understand how GOAWAY and QUIC 0 RTT rejections are handled. Look at the mobile integration tests in test/integration/ and consider adding retry logic for non fatal errors.
Tech stack
cpp
Domain
backendinfrastructuremobile
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25