From 6bd718e0db33efd2fea9872cf48b0876b9983f02 Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Mon, 29 Jan 2024 16:08:52 -0500 Subject: [PATCH] Add known issue for AWS S3 performance in 8.12 (#37766) (#37767) (cherry picked from commit 51f5cb4e4d23f122cc546c670cb3912c2c3f0184) Co-authored-by: Craig MacKenzie --- CHANGELOG.asciidoc | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/CHANGELOG.asciidoc b/CHANGELOG.asciidoc index 3305b1989b69..071357c104a2 100644 --- a/CHANGELOG.asciidoc +++ b/CHANGELOG.asciidoc @@ -7,6 +7,18 @@ === Beats version 8.12.0 https://github.com/elastic/beats/compare/v8.11.4\...v8.12.0[View commits] +==== Known Issues + +*Affecting all Beats* + +Performance regression in AWS S3 inputs using SQS notification. + +In 8.12 the default memory queue flush interval was raised from 1 second to 10 seconds. In many configurations this improves performance because it allows the output to batch more events per round trip, which improves efficiency. However, the SQS input has an extra bottleneck that interacts badly with the new value. For more details see {issue}37754[37754]. + +If you are using the Elasticsearch output, and your output configuration uses a performance preset, switch it to `preset: latency`. If you use no preset or use `preset: custom`, then set `queue.mem.flush.timeout: 1` in your queue or output configuration. + +If you are not using the Elasticsearch output, set `queue.mem.flush.timeout: 1` in your queue or output configuration. + ==== Breaking changes *Heartbeat*