- 
                Notifications
    You must be signed in to change notification settings 
- Fork 3.5k
Fix/avoid oom accumulation in bufftok #17293
New issue
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
          
     Closed
      
      
            andsel
  wants to merge
  16
  commits into
  elastic:main
from
andsel:fix/avoid_oom_accumulation_in_bufftok
  
      
      
   
      
    
                
     Closed
            
            Fix/avoid oom accumulation in bufftok #17293
                    andsel
  wants to merge
  16
  commits into
  elastic:main
from
andsel:fix/avoid_oom_accumulation_in_bufftok
  
      
      
   
              
            Conversation
  
    
      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
    
  
  
    
    …once reached the next separator
| This pull request does not have a backport label. Could you fix it @andsel? 🙏 
 | 
eea9f37    to
    fc3f3e4      
    Compare
  
    …ments beloging to an already incomplete overrun token till next separator is found
e23c263    to
    71daf70      
    Compare
  
    | 
 | 
| 💛 Build succeeded, but was flaky
 Failed CI StepsHistory
 cc @andsel | 
      
        
      
      
  
    4 tasks
  
      
        
      
      
  
    7 tasks
  
    
  andsel 
      added a commit
        to andsel/logstash
      that referenced
      this pull request
    
      Jun 18, 2025 
    
    
      
  
    
      
    
  
… the append to the DataSplitter
| Closed because squashed into the parent PR #17229 | 
    
  andsel 
      added a commit
        to andsel/logstash
      that referenced
      this pull request
    
      Jul 2, 2025 
    
    
      
  
    
      
    
  
… the append to the DataSplitter
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      
  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.
  
    
  
    




TODO to be applied on top of #17229
Release notes
What does this PR do?
Why is it important/What is the impact to the user?
Checklist
Author's Checklist
How to test this PR locally
1 Test on stdin
Test running the same configuration as in logstash-plugins/logstash-codec-json_lines#43 against this branch, it shouldn't go in OOM.
2 Test on TCP
Use the 1Gb big one line file generated at step 1, with same heap limitation. Run Logstash with following pipeline:
and feed data in with
netcat, like in:cat /path/to/big_single_line.json | netcat localhost 12343 Test with file input
Use the 1Gb big one line file generated at step 1, with same heap limitation. Run Logstash with following pipeline:
Related issues
Logs
Before this PR, but with branch in #17229
With this fix: