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.

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

[aws] Update max_number_of_messages doc #40508

Merged
merged 1 commit into from
Aug 13, 2024
Merged
Changes from all commits
Commits
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 x-pack/filebeat/docs/inputs/input-aws-s3.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -268,13 +268,13 @@ The default is `10 MiB`.
==== `max_number_of_messages`

The maximum number of SQS messages that can be inflight at any time. Defaults
to 5. When processing large amount of large size S3 objects and each object has
large amount of events, if this parameter sets too high, it can cause the input
to process too many messages concurrently, overload the agent and cause ingest failure.
We recommend to keep the default value 5 and use the
to 5. Setting this parameter too high can overload Elastic Agent and cause
ingest failures in situations where the SQS messages contain many S3 objects
or the S3 objects themselves contain large numbers of messages.
We recommend to keep the default value 5 and use the `Balanced` or `Optimized for
Throughput` setting in the
{fleet-guide}/es-output-settings.html#es-output-settings-performance-tuning-settings[preset]
option to tune your Elastic Agent performance. You can optimize for throughput,
scale, latency, or you can choose a balanced (the default) set of performance specifications.
options to tune your Elastic Agent performance.

[id="input-{type}-parsers"]
[float]
Expand Down
Loading