Logstash-filter-aggregate (2.5.0) fails with latest logstash (5.0.2)

Hi,

after update logstash from 5.0.0 to 5.0.2 my pipeline fails when aggregating events with logstash-filter-aggregate.

Is something changed with aggragate syntax? It's a compatibility issue?

Sending Logstash's logs to /var/log/logstash which is now configured via log4j2.properties
SystemStackError: stack level too deep
    synchronize at org/jruby/ext/thread/Mutex.java:149
         filter at /usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-filter-aggregate-2.5.0/lib/logstash/filters/aggregate.rb:427
   multi_filter at /usr/share/logstash/logstash-core/lib/logstash/filters/base.rb:156
           each at org/jruby/RubyArray.java:1613
   multi_filter at /usr/share/logstash/logstash-core/lib/logstash/filters/base.rb:153
   multi_filter at /usr/share/logstash/logstash-core/lib/logstash/filter_delegator.rb:41
     initialize at (eval):441
           each at org/jruby/RubyArray.java:1613
     initialize at (eval):432
           call at org/jruby/RubyProc.java:281
    filter_func at (eval):302
   filter_batch at /usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:260
           call at org/jruby/RubyProc.java:281
           each at /usr/share/logstash/logstash-core/lib/logstash/util/wrapped_synchronous_queue.rb:186
           each at org/jruby/RubyHash.java:1342
           each at /usr/share/logstash/logstash-core/lib/logstash/util/wrapped_synchronous_queue.rb:185
   filter_batch at /usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:258
    worker_loop at /usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:246
  start_workers at /usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:225

Thank you,

Jesús López

This issue is being discussed here => https://github.com/logstash-plugins/logstash-filter-aggregate/issues/51

This issue has been resolved here => https://github.com/logstash-plugins/logstash-filter-aggregate/issues/51

Thanks to @fbaligand

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.