we try to do some simple kind of fail over for Logstash so we setup a second instance and now we activated the loadbalance on filebeat. We also have some pipelines where we´re using aggregate and relying on previous events.
Is loadbalance even possible with this circumstances or should we link those pipelines with aggregate only to a single logstash instance?
The aggregate filter requires all related events to pass through a single thread, which limits performance, scalability and the ability to build a highly available pipeline. If you can describe your data and what you are looking to use the aggregate filter for, maybe someone can come up with alternate approaches that does not suffer from these quite severe restrictions.
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.