From 238f3c1733aa1edf78627c86d49cf8bd45b09bf6 Mon Sep 17 00:00:00 2001 From: Robin Clarke Date: Wed, 1 Jul 2020 14:05:15 +0200 Subject: [PATCH] Added detail about pipeline.batch.size corresponding to elasticsearch batch size --- docs/index.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.asciidoc b/docs/index.asciidoc index a8743aab8..ada116847 100644 --- a/docs/index.asciidoc +++ b/docs/index.asciidoc @@ -77,7 +77,7 @@ Each Elasticsearch output is a new client connected to the cluster: * it has to initialize the client and connect to Elasticsearch (restart time is longer if you have more clients) * it has an associated connection pool -In order to minimize the number of open connections to Elasticsearch, maximize the bulk size and reduce the number of "small" bulk requests (which could easily fill up the queue), it is usually more efficient to have a single Elasticsearch output. +In order to minimize the number of open connections to Elasticsearch, maximize the bulk size and reduce the number of "small" bulk requests (which could easily fill up the queue), it is usually more efficient to have a single Elasticsearch output. Bulk request size is set with the logstash configuration `pipeline.batch.size`. Example: [source,ruby]