# Logstash 5.4.0 stuck/hang after processing certain amount of data (http-output plugin)

**URL:** https://discuss.elastic.co/t/logstash-5-4-0-stuck-hang-after-processing-certain-amount-of-data-http-output-plugin/92252
**Category:** Logstash
**Created:** [July 7, 2017, 10:20am UTC](https://discuss.elastic.co/t/logstash-5-4-0-stuck-hang-after-processing-certain-amount-of-data-http-output-plugin/92252 "2017-07-07T10:20:06Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![singhashutosh111](https://avatars.discourse-cdn.com/v4/letter/s/a8b319/32.png) [@singhashutosh111](https://discuss.elastic.co/u/singhashutosh111)
#### Post date: [July 7, 2017, 10:20am UTC](https://discuss.elastic.co/t/logstash-5-4-0-stuck-hang-after-processing-certain-amount-of-data-http-output-plugin/92252/1 "2017-07-07T10:20:06Z")

</div>

Hi All,

I am using Logstash 5.4.0 for logs parsing and data ingestion. Issue is that the Logstash becomes unresponsive after processing around 2M log lines.

Hardware Configuration is:  
• RHEL 7  
• 16 Cores CPU, 64 GB RAM  
• Java 8

Logstash Config:  
• Logstash version 5.4.0  
• -Xmx=4g  
• -Xms=4g  
• pipeline.batch.size: 125  
• pipeline.output.workers: 16  
• pipeline.batch.delay: 5

logstash conf code for output section:

http {  
http\_method =\> "post"  
url =\> "[http://localhost:8080/test](http://localhost:8080/test)"  
format =\> "message"  
headers =\> {"Content-Type" =\> "application/json"}  
content\_type =\> "application/json"  
message =\> '%{message}'  
pool\_max =\> 400  
pool\_max\_per\_route =\> 200  
}

Any help on this will be highly appreciated.

Also attaching the logstash stats in text file for the reference.

JVM Stats:  
{  
"host": "test.dev.fco",  
"version": "5.4.0",  
"http\_address": "127.0.0.1:9600",  
"id": "9dbbab77-5708-4fb5-9164-8186218c43ea",  
"name": "test.dev.fco",  
"jvm": {  
"threads": {  
"count": 88,  
"peak\_count": 1305  
},  
"mem": {  
"heap\_used\_in\_bytes": 394557488,  
"heap\_used\_percent": 9,  
"heap\_committed\_in\_bytes": 758067200,  
"heap\_max\_in\_bytes": 4181590016,  
"non\_heap\_used\_in\_bytes": 135493912,  
"non\_heap\_committed\_in\_bytes": 144883712,  
"pools": {  
"survivor": {  
"peak\_used\_in\_bytes": 17891328,  
"used\_in\_bytes": 9084368,  
"peak\_max\_in\_bytes": 113377280,  
"max\_in\_bytes": 113377280,  
"committed\_in\_bytes": 17891328  
},  
"old": {  
"peak\_used\_in\_bytes": 489065328,  
"used\_in\_bytes": 323718520,  
"peak\_max\_in\_bytes": 3160866816,  
"max\_in\_bytes": 3160866816,  
"committed\_in\_bytes": 597045248  
},  
"young": {  
"peak\_used\_in\_bytes": 143130624,  
"used\_in\_bytes": 61754600,  
"peak\_max\_in\_bytes": 907345920,  
"max\_in\_bytes": 907345920,  
"committed\_in\_bytes": 143130624  
}  
}  
},  
"gc": {  
"collectors": {  
"old": {  
"collection\_time\_in\_millis": 14120,  
"collection\_count": 229  
},  
"young": {  
"collection\_time\_in\_millis": 151233,  
"collection\_count": 11051  
}  
}  
},  
"uptime\_in\_millis": 2579583  
}  
}

# Hot Threads: ::: {} Hot threads at 2017-07-07T01:42:56-06:00, busiestThreads=3:

## 46.61 % of cpu usage, state: waiting, thread name: '[main]\>worker4' java.lang.Object.wait(Native Method) java.lang.Object.wait(Object.java:460) org.jruby.RubyThread$SleepTask.run(RubyThread.java:1050) org.jruby.RubyThread.executeBlockingTask(RubyThread.java:1066) org.jruby.RubyThread.wait\_timeout(RubyThread.java:1414) org.jruby.ext.thread.Queue.pop(Queue.java:152) org.jruby.ext.thread.Queue.pop(Queue.java:127) org.jruby.ext.thread.Queue$INVOKER$i$pop.call(Queue$INVOKER$i$pop.gen) org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:134) rubyjit.LogStash::Outputs::Http$$send\_events\_53b66f5675683db7f49396d05b16a7190f3381571560911714.chained\_1\_rescue\_2$RUBY$SYNTHETIC\_\_file\_\_(/opt/ca/axa/logparser/logstash-5.4.0/vendor/bundle/jruby/1.9/gems/logstash-output-http-4.1.0/lib/logstash/outputs/http.rb:141)

## 36.53 % of cpu usage, state: waiting, thread name: '[main]\>worker5' java.lang.Object.wait(Native Method) java.lang.Object.wait(Object.java:460) org.jruby.RubyThread$SleepTask.run(RubyThread.java:1050) org.jruby.RubyThread.executeBlockingTask(RubyThread.java:1066) org.jruby.RubyThread.wait\_timeout(RubyThread.java:1414) org.jruby.ext.thread.Queue.pop(Queue.java:152) org.jruby.ext.thread.Queue.pop(Queue.java:127) org.jruby.ext.thread.Queue$INVOKER$i$pop.call(Queue$INVOKER$i$pop.gen) org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:134) rubyjit.LogStash::Outputs::Http$$send\_events\_53b66f5675683db7f49396d05b16a7190f3381571560911714.chained\_1\_rescue\_2$RUBY$SYNTHETIC\_\_file\_\_(/opt/ca/axa/logparser/logstash-5.4.0/vendor/bundle/jruby/1.9/gems/logstash-output-http-4.1.0/lib/logstash/outputs/http.rb:141)

## 6.56 % of cpu usage, state: waiting, thread name: '[main]\>worker2' java.lang.Object.wait(Native Method) java.lang.Object.wait(Object.java:460) org.jruby.RubyThread$SleepTask.run(RubyThread.java:1050) org.jruby.RubyThread.executeBlockingTask(RubyThread.java:1066) org.jruby.RubyThread.wait\_timeout(RubyThread.java:1414) org.jruby.ext.thread.Queue.pop(Queue.java:152) org.jruby.ext.thread.Queue.pop(Queue.java:127) org.jruby.ext.thread.Queue$INVOKER$i$pop.call(Queue$INVOKER$i$pop.gen) org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:134) rubyjit.LogStash::Outputs::Http$$send\_events\_53b66f5675683db7f49396d05b16a7190f3381571560911714.chained\_1\_rescue\_2$RUBY$SYNTHETIC\_\_file\_\_(/opt/ca/axa/logparser/logstash-5.4.0/vendor/bundle/jruby/1.9/gems/logstash-output-http-4.1.0/lib/logstash/outputs/http.rb:141)

Thanks in advance.

Ashutosh

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 4, 2017, 10:20am UTC](https://discuss.elastic.co/t/logstash-5-4-0-stuck-hang-after-processing-certain-amount-of-data-http-output-plugin/92252/2 "2017-08-04T10:20:19Z")

</div>

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