Skip to content

Commit

Permalink
Update max_number_of_messages doc (#40508) (#40514)
Browse files Browse the repository at this point in the history
(cherry picked from commit 0567022)

Co-authored-by: kaiyan-sheng <[email protected]>
  • Loading branch information
mergify[bot] and kaiyan-sheng authored Aug 14, 2024
1 parent c734a74 commit 345d971
Showing 1 changed file with 6 additions and 6 deletions.
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 @@ -266,13 +266,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

0 comments on commit 345d971

Please sign in to comment.