Skip to content
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

multithreading: minor style updates #1504

Merged
merged 1 commit into from
Nov 7, 2024
Merged

multithreading: minor style updates #1504

Show file tree
Hide file tree
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
12 changes: 6 additions & 6 deletions administration/multithreading.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,23 +6,23 @@ description: Learn how to run Fluent Bit in multiple threads for improved scalab

Fluent Bit has one event loop to handle critical operations, like managing
timers, receiving internal messages, scheduling flushes, and handling retries.
This event loop runs in Fluent Bit's main thread.
This event loop runs in the main Fluent Bit thread.

To free up resources in the main thread, you can configure
[inputs](../pipeline/inputs/README.md) and [outputs](../pipeline/outputs/README.md)
to run in their own self-contained threads. However, inputs and outputs implement
multithreading in distinct ways: inputs can run in **threaded** mode, and outputs
can use one or more **workers**.
multithreading in distinct ways: inputs can run in threaded mode, and outputs
can use one or more workers.

Threading also affects certain processes related to inputs and outputs. For example,
Threading also affects certain processes related to inputs and outputs. For example,
[filters](../pipeline/filters/README.md) always run in the main thread, but
[processors](../pipeline/processors/README.md) run in the self-contained threads of
their respective inputs or outputs, if applicable.

## Inputs

When inputs collect telemetry data, they can either perform this process
inside Fluent Bit's main thread or inside a separate dedicated thread. You can
inside the main Fluent Bit thread or inside a separate dedicated thread. You can
configure this behavior by enabling or disabling the `threaded` setting.

All inputs are capable of running in threaded mode, but certain inputs always
Expand All @@ -33,7 +33,7 @@ run in threaded mode regardless of configuration. These always-threaded inputs a
- [Process Exporter Metrics](../pipeline/inputs/process-exporter-metrics.md)
- [Windows Exporter Metrics](../pipeline/inputs/windows-exporter-metrics.md)

Inputs are not internally aware of multithreading. If an input runs in threaded
Inputs aren't internally aware of multithreading. If an input runs in threaded
mode, Fluent Bit manages the logistics of that input's thread.

## Outputs
Expand Down
1 change: 1 addition & 0 deletions vale-styles/FluentBit/Spelling-exceptions.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,6 +89,7 @@ matchers
Minishift
minikube
MTTx
multithreading
namespace
namespaces
Nginx
Expand Down