grafana/pyroscope

Add an instance-level inflight bytes limit to the distributor

Open

#5,437 opened on Jul 28, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (528 forks)batch import
good first issue

Repository metrics

Stars
 (9,041 stars)
PR merge metrics
 (Avg merge 5d 7h) (62 merged PRs in 30d)

Description

An application-level flag such as -distributor.max-inflight-bytes can protect distributors from being OOMKilled when segment writers experience slowdowns or outages.

Prior art:

Should be opt-in and apply for both the regular (sync) and the async write path.

Contributor guide

Research direction
Explore pyroscope's distributor write path, review the referenced Mimir and Loki implementations of inflight byte limits, and identify where to add the flag and enforce it for both sync and async methods.
Tech stack
go
Domain
backend
Issue type
Feature
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.
1-3 hours
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
GoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65