### 執行模型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)獲取更多信息。