From 8993a0f90847a53444c00f1b41cb61640af82179 Mon Sep 17 00:00:00 2001 From: Karen Metts Date: Tue, 9 Nov 2021 18:55:58 -0500 Subject: [PATCH 1/3] Doc: Edit documentation for executor_threads --- CHANGELOG.md | 1 + docs/index.asciidoc | 8 ++++---- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 769d3637..7b32a92a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,6 @@ ## Unreleased - Fix: update to Gradle 7 [#432](https://github.com/logstash-plugins/logstash-input-beats/pull/432) + - [DOC] Edit documentation for `executor_threads` [#tbd](https://github.com/logstash-plugins/logstash-input-beats/pull/tbd) ## 6.2.1 - Fix: LS failing with `ssl_peer_metadata => true` [#431](https://github.com/logstash-plugins/logstash-input-beats/pull/431) diff --git a/docs/index.asciidoc b/docs/index.asciidoc index 98becc4e..93e0d547 100644 --- a/docs/index.asciidoc +++ b/docs/index.asciidoc @@ -232,14 +232,14 @@ Refer to <> for detailed info * Default value is 1 executor thread per CPU core The number of threads to be used to process incoming beats requests. -By default Beats input will create a number of threads equals to 2*CPU cores to handle incoming connections, -reading from the established sockets and execute most of the tasks related to network connection managements, -except the parsing of Lumberjack protocol that's offloaded to a dedicated thread pool. +By default the Beats input creates a number of threads equal to 2*CPU cores. +These threads handle incoming connections, reading from established sockets, and executing most of the tasks related to network connection management. +Parsing the Lumberjack protocol is offloaded to a dedicated thread pool. Generally you don't need to touch this setting. In case you are sending very large events and observing "OutOfDirectMemory" exceptions, you may want to reduce this number to half or 1/4 of the CPU cores. -This will reduce the number of threads decompressing batches of data into direct memory. +This change reduces the number of threads decompressing batches of data into direct memory. However, this will only be a mitigating tweak, as the proper solution may require resizing your Logstash deployment, either by increasing number of Logstash nodes or increasing the JVM's Direct Memory. From 03bf6271239316d793c09976c863beb47076218e Mon Sep 17 00:00:00 2001 From: Karen Metts <35154725+karenzone@users.noreply.github.com> Date: Tue, 9 Nov 2021 18:59:56 -0500 Subject: [PATCH 2/3] Add PR number to changelog --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 7b32a92a..c72969f5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,6 @@ ## Unreleased - Fix: update to Gradle 7 [#432](https://github.com/logstash-plugins/logstash-input-beats/pull/432) - - [DOC] Edit documentation for `executor_threads` [#tbd](https://github.com/logstash-plugins/logstash-input-beats/pull/tbd) + - [DOC] Edit documentation for `executor_threads` [#435](https://github.com/logstash-plugins/logstash-input-beats/pull/435) ## 6.2.1 - Fix: LS failing with `ssl_peer_metadata => true` [#431](https://github.com/logstash-plugins/logstash-input-beats/pull/431) From 752a7ed4a99c71d96aa44c764e4f66bbd6339b2b Mon Sep 17 00:00:00 2001 From: Karen Metts Date: Wed, 10 Nov 2021 18:29:25 -0500 Subject: [PATCH 3/3] Bumo to v6.2.2 --- CHANGELOG.md | 2 +- VERSION | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index c72969f5..cb8f825f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,4 +1,4 @@ -## Unreleased +## 6.2.2 - Fix: update to Gradle 7 [#432](https://github.com/logstash-plugins/logstash-input-beats/pull/432) - [DOC] Edit documentation for `executor_threads` [#435](https://github.com/logstash-plugins/logstash-input-beats/pull/435) diff --git a/VERSION b/VERSION index 024b066c..ca063943 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -6.2.1 +6.2.2