Skip to content

chore(docs): Emphasize the "may" bit of the backpressure docs #18457

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jszwedko merged 1 commit into from
Sep 1, 2023
Merged

chore(docs): Emphasize the "may" bit of the backpressure docs #18457

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions website/content/en/docs/about/concepts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,8 +80,8 @@ View the full configuration options for buffers [here](/docs/reference/configura

If a sink's buffer fills up and is configured to provide backpressure, that backpressure will propagate to any connected
transforms, which will also propagate to the sources. The sources attempt to propagate backpressure to
whichever system is providing data. The exact mechanism varies with the source. For example, HTTP sources may
reject requests with an HTTP 429 error (Too Many Requests), or pull-based sources such as Kafka may slow down fetching new events.
whichever system is providing data. The exact mechanism varies with the source. For example, HTTP sources _may_
reject requests with an HTTP 429 error (Too Many Requests), or pull-based sources such as Kafka _may_ slow down fetching new events.

Since Vector allows configuring components as a directed acyclic graph, understanding how backpressure works when there
are multiple sinks or sources involved is important.
Expand Down