We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
json_lines
3.2.0
input buffer full
When using the json_lines codec > 3.2.0 with versions of Logstash < 8.17.1, the following error may be emitted, crashing the pipelines:
8.17.1
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)",
This will most typically occur when using the Logstash integration plugin to ship data between two Logstashes.
This is due to an issue fixed in #16760, but the issue is likely present in Logstash 8.16.0, 8.16.1 and 8.17.0
8.16.0
8.16.1
8.17.0
When using the Logstash->Logstash flow, this can be mitigated by:
8.16.2
8.15
1.0.4
When using the json_lines codec , this can be mitigated by:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When using the
json_lines
codec >3.2.0
with versions of Logstash <8.17.1
, the following error may be emitted, crashing the pipelines:This will most typically occur when using the Logstash integration plugin to ship data between two Logstashes.
This is due to an issue fixed in #16760, but the issue is likely present in Logstash
8.16.0
,8.16.1
and8.17.0
When using the Logstash->Logstash flow, this can be mitigated by:
8.16.2
, or any Logstash in the8.15
series. AND/OR1.0.4
.When using the
json_lines
codec , this can be mitigated by:8.16.2
, or any Logstash in the8.15
series.The text was updated successfully, but these errors were encountered: