From 395bb990e73816537c5893eedd049c3645d89391 Mon Sep 17 00:00:00 2001 From: George Angelopoulos Date: Wed, 26 Nov 2014 16:09:31 +0200 Subject: [PATCH] docs: remove double word --- docs/1.4.2/life-of-an-event.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/1.4.2/life-of-an-event.md b/docs/1.4.2/life-of-an-event.md index f7dd640..f5c7191 100644 --- a/docs/1.4.2/life-of-an-event.md +++ b/docs/1.4.2/life-of-an-event.md @@ -88,7 +88,7 @@ elasticsearch. Small queue sizes mean that logstash simply blocks and stalls safely during times of load or other temporary pipeline problems. There are two alternatives to this - unlimited queue length and dropping messages. Unlimited queues grow -grow unbounded and eventually exceed memory causing a crash which loses all of +unbounded and eventually exceed memory causing a crash which loses all of those messages. Dropping messages is also an undesirable behavior in most cases. At a minimum, logstash will have probably 3 threads (2 if you have no filters).