Logstash 8.17.0 Release Notes

If the jvm.options file was modified and not overwritten with the newest version, you may see a "deserialize invocation error" message, causing the pipeline to crash. Users are affected if the Persistent Queue (PQ) is enabled, and the pipeline is processing messages larger than 20MB.

Solution: Apply the default change contained in the newer jvm.options file, as seen in this example.

If you are using json_lines codec 3.2.0 (or later) with Logstash 8.16.0, 8.16.1, or 8.17.0, you may see an error similar to this one, crashing the pipelines:

unable to process event. {:message=>"input buffer full", :class=>"Java::JavaLang::IllegalStateException", :backtrace=>["org.logstash.common.BufferedTokenizerExt.extract(BufferedTokenizerExt.java:83)", "usr.share.logstash.vendor.bundle.jruby.$3_dot_1_dot_0.gems.logstash_minus_codec_minus_json_lines_minus_3_dot_2_dot_2.lib.logstash.codecs.json_lines.RUBY$method$decode$0(/usr/share/logstash/vendor/bundle/jruby/3.1.0/gems/logstash-codec-json_lines-3.2.2/lib/logstash/codecs/json_lines.rb:69)", "org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:165)", "org.jruby.internal.runtime.methods.MixedModeIRMethod.call(MixedModeIRMethod.java:185)",

The issue was fixed in https://github.com/elastic/logstash/pull/16760.

This problem is most likely to be seen when you are using the Logstash integration plugin to ship data between two Logstash instances, but may appear in other situations, too.

Workaround for Logstash-to-Logstash communication

The Logstash-to-Logstash issue can be mitigated by:

Workaround for other json_lines codec situations

Other json_lines codec issues can be mitigated by: