Skip to content

Add HTTP body compression between pipeline-manager and pipelines, raise the limit#5626

Open
Karakatiza666 wants to merge 2 commits intomainfrom
issue5624
Open

Add HTTP body compression between pipeline-manager and pipelines, raise the limit#5626
Karakatiza666 wants to merge 2 commits intomainfrom
issue5624

Conversation

@Karakatiza666
Copy link
Contributor

@Karakatiza666 Karakatiza666 commented Feb 13, 2026

The issue was caused by the artifical RESPONSE_SIZE_LIMIT for the uncompressed response body size for requests from pipeline-manager to the pipeline server.

  • I added HTTP response compression to the pipeline process server, so non-streaming requests proxied by pipeline-manager (e.g., circuit profile, stats) are transferred compressed on the internal hop.
  • Raised RESPONSE_SIZE_LIMIT from 20 MiB to 100 MiB since the limit applies to the decompressed body and large circuit profiles can exceed 20 MiB.
  • Prevented compression on streaming proxy requests (/egress, /ingress, time series streams) by stripping Accept-Encoding and disabling awc auto-decompression, avoiding gzip frame buffering that blocks streaming pipeline-manager clients' requests.

Fix #5624: [PROFILE] The circuit profile should be compressed

Testing:
With an artificially lowered RESPONSE_SIZE_LIMIT I saw the same error when downloading the support bundle for a small pipeline.
With these changes, after recompiling the pipeline-manager and the pipeline Performance, Logs and Changes Stream tabs that use proxied streaming requests worked as expected, and I was able to download the support bundle with valid contents.

…r and pipelines, raise the limit

Signed-off-by: Karakatiza666 <bulakh.96@gmail.com>
@Karakatiza666 Karakatiza666 requested a review from gz February 13, 2026 10:21
Signed-off-by: feldera-bot <feldera-bot@feldera.com>
@Karakatiza666 Karakatiza666 marked this pull request as ready for review February 13, 2026 10:52
@lalithsuresh
Copy link
Contributor

lalithsuresh commented Feb 13, 2026

This needs unit and integration tests. I'm also nervous about disabling compression on proxied streaming requests.

@Karakatiza666
Copy link
Contributor Author

The compression was already disabled for streaming requests because it breaks the on-demand data streaming - the stream does not send the data as soon as it's available and instead buffers to collect a complete encoding chunk

.headers()
.into_iter()
.filter(|(h, _)| *h != "connection")
.filter(|(h, _)| *h != "connection" && *h != "accept-encoding")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks too subtle. I hope we find a more bullet-proof way not to compress stuff that shouldn't be compressed.

Copy link
Contributor Author

@Karakatiza666 Karakatiza666 Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, for now we have abstracted the proxying to the pipeline process behind two functions - streaming and non-streaming

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[PROFILE] The circuit profile should be compressed

4 participants