Add decode_size_limit_bytes option.#30
Open
andrewvc wants to merge 1 commit intologstash-plugins:mainfrom
Open
Add decode_size_limit_bytes option.#30andrewvc wants to merge 1 commit intologstash-plugins:mainfrom
andrewvc wants to merge 1 commit intologstash-plugins:mainfrom
Conversation
| it "should raise an error if the max bytes are exceeded" do | ||
| expect { | ||
| subject.decode(maximum_payload << "z") | ||
| }.to raise_error(RuntimeError, "input buffer full") |
Contributor
There was a problem hiding this comment.
is there a way to provide more context to this exception? input buffer full feels a little vague, or am I missing something?
Contributor
Author
There was a problem hiding this comment.
Unfortunately that exception is provided by the FileWatch library, so it'd require a patch there. I should probably wrap and re-raise it.
Contributor
Author
There was a problem hiding this comment.
I just submitted https://github.com/jordansissel/ruby-filewatch/pull/82/files to enable us to catch a more precise exception.
| # Maximum number of bytes for a single line before a fatal exception is raised | ||
| # which will stop Logsash. | ||
| # The default is 20MB which is quite large for a JSON document | ||
| config :decode_size_limit_bytes, :validate => :number, :default => 20 * (1024 * 1024) # 20MB |
Contributor
There was a problem hiding this comment.
- Is
decodethe right name? The description says this is bytes for a line, but then we call itdecodewhich isn't something mentioned elsewhere in the docs. - Exceeding this will cause a fatal error in Logstash and stop the process? Is this the desired behavior?
Contributor
There was a problem hiding this comment.
If the size limit is exceeded, where do we show that this exception will terminate Logstash? I don't see it when I read through the code.
Contributor
Test planUsed 1 line big json file (~1GB), limited the Java heap to 512Mb, and processed with a file input plugin. It goes in OOM Generate one big json fileUse the script to generate it: require "json"
part = [
{:name => "Jannik", :surname => "Sinner"},
{:name => "Novak", :surname => "Djokovic"},
{:name => "Rafa", :surname => "Nadal"},
{:name => "Roger", :surname => "Federer"},
{:name => "Pete", :surname => "Sampras"},
{:name => "André", :surname => "Agassi"},
{:name => "Rod", :surname => "Laver"},
{:name => "Ivan", :surname => "Lendl"},
{:name => "Bjorn", :surname => "Borg"},
{:name => "John", :surname => "McEnroe"},
{:name => "Jimmy", :surname => "Connors"}
]
json_part = JSON.generate(part)
out_file = File.open("big_single_line.json", "a")
out_file.write "{"
counter = 1
desired_size = 1024 * 1024 * 1024
actual_size = 0
while actual_size < desired_size do
json_fragment = "\"field_#{counter}\": #{json_part}"
actual_size += json_fragment.size
if actual_size < desired_size
json_fragment += ","
end
counter += 1
out_file.write json_fragment
end
out_file.write "}\r\n"
out_file.flush
puts "Done! output file is #{out_file.size} bytes"
out_file.closeConfigure LogstashIn and execute the pipeline Configure this patch PR, in "logstash-codec-json_lines"with "logstash-codec-json_lines", :path => "/Users/andrea/workspace/logstash_plugins/logstash-codec-json_lines"and execute bin/logstash-plugin install --no-verifyResultIt fails with following logs |
Contributor
|
The problem with this approach is that the size limit works only when the data is fully loaded in memory: In such case, as the exception's stacktrace exposes: the problem is throw before, when the data are still being read from the IO. Can't be catched by this codec because it's raised by the input |
This was referenced Aug 28, 2024
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #29 . This is most useful when people accidentally use this codec on something that is not properly newline delimited. That can easily lead to an OOM.
Superseded by #43