I am trying to make a config that does a batch of indexing, then an elasticsearch filter query to find documents that need an update to be marked as stale (via a new event created in a subsequent ruby filter). It's important that my filter runs after all indexing is complete. What I have found is t…

[image] jdmcalee: With the filter disabled, the events are output in the expected order. Can anyone explain what is going on? This is one of the effects of javafication. Events can get re-ordered even when you use a single pipeline worker. You could get the old behaviour using pipeline.java_…

Discuss the Elastic Stack

Question about filter effects on event handling order

Elastic Stack Logstash

jdmcalee (Justin McAleer) June 11, 2019, 4:21pm 3

does that mean that the aggregate filter can't be trusted either?

Topic		Replies	Views
Batch size in logstash Logstash	8	998	December 7, 2019
Ruby filter processes events in incorrect order Logstash	8	1496	April 2, 2018
Logstash events out of order Logstash	3	2077	April 29, 2020
Aggregate filter bug with java execution engine Logstash	4	669	July 24, 2019
How to process messages strictly in the order they arrive? Logstash	5	5085	July 6, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Question about filter effects on event handling order

Related topics