From 35f27bf6e77da4b00dbb874fc1af6e6bdc95e4b6 Mon Sep 17 00:00:00 2001 From: kaiyan-sheng Date: Tue, 13 Aug 2024 15:57:26 -0600 Subject: [PATCH] Update max_number_of_messages doc (#40508) (cherry picked from commit 0567022433448598279a68fc9aedbd25b86f6f15) --- x-pack/filebeat/docs/inputs/input-aws-s3.asciidoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/x-pack/filebeat/docs/inputs/input-aws-s3.asciidoc b/x-pack/filebeat/docs/inputs/input-aws-s3.asciidoc index 01002c684e16..ca3f854f11e0 100644 --- a/x-pack/filebeat/docs/inputs/input-aws-s3.asciidoc +++ b/x-pack/filebeat/docs/inputs/input-aws-s3.asciidoc @@ -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]