envoyproxy/envoy

Questions: what does it mean to get 507 code from envoy?

Open

#15,211 opened on Feb 26, 2021

View on GitHub
 (10 comments) (1 reaction) (0 assignees)C++ (5,373 forks)batch import
area/docshelp wanted

Repository metrics

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

Description

Title: what does it mean to get 507 code from envoy?

Description: Hi, I just get response code: 507 with response text: "exceeded request buffer limit while retrying upstream". And I just cant understand what happend, because the only trace of that error I can find is link to the place where error was raised in source code: https://github.com/envoyproxy/envoy/blob/main/source/common/router/router.cc#L687 But I still just don't get what exactly happenned there. Could you please explain it?

Relevant Links: https://github.com/envoyproxy/envoy/blob/main/source/common/router/router.cc#L687

P.S. mb that info should be described in documentation?

Contributor guide

Research direction
Research Envoy's request buffer limit configuration and retry logic. The error 'exceeded request buffer limit while retrying upstream' occurs when Envoy's internal buffer for request data is full and the upstream retry cannot proceed. Look into the 'max request bytes' and buffer limits in Envoy's HTTP connection manager and router filter.
Tech stack
None
Domain
networking
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70