### 执行模型Execution Model Logstash事件处理管道协调inputs、filters和outputs的执行。 Each input stage in the Logstash pipeline runs in its own thread.（这句直接翻译应该是每个input阶段在Logstash中都有自己独立的线程。但是，我感觉他想表达的可能是Logstash的input、filter、output三个阶段都有自己独立的线程。）Inputs将事件写入内存(默认)或磁盘上的中央队列。每个管道中的工作线程从队列中取走一部分事件。通过配置的filters处理这些事件，然后通过outputs处理filters处理过的时间。工作线程的多少和取走部分的大小是可以配置的。（参见：[Tuning and Profiling Logstash Performance](https://www.elastic.co/guide/en/logstash/current/tuning-logstash.html)）。 这一段的原文：Each input stage in the Logstash pipeline runs in its own thread. Inputs write events to a central queue that is either in memory (default) or on disk. Each pipeline worker thread takes a batch of events off this queue, runs the batch of events through the configured filters, and then runs the filtered events through any outputs. The size of the batch and number of pipeline worker threads are configurable (see [Tuning and Profiling Logstash Performance](https://www.elastic.co/guide/en/logstash/current/tuning-logstash.html)). 默认情况下，Logstash使用每个阶段中内存中的消息队列来缓存事件。如果Logstash被不安全的停止，则会丢失内存中的数据。要降低数据丢失的风险，可以打开Logstash持久化到磁盘的功能。参见[Persistent Queues](https://www.elastic.co/guide/en/logstash/current/persistent-queues.html)获取更多信息。