Skip to content
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

logstash stalled/blocked - 1.5.0rc2 #2846

Closed
seventy-7 opened this issue Mar 18, 2015 · 10 comments
Closed

logstash stalled/blocked - 1.5.0rc2 #2846

seventy-7 opened this issue Mar 18, 2015 · 10 comments

Comments

@seventy-7
Copy link

Hello devs,

Have been facing a persistent issue. I've been seeing logstash receivers stalling regularly (every 15min). The process will stop receiving input and all threads look blocked. The process never recovers. logstash inputs become in a closed wait status. and the process is rendered useless. From my understanding of the event pipeline, if the output may become busy, the pipeline can get blocked but will recover. In this case it doesnt recover.

Setup details:

20 logstash forwarders -> 5 logstash receivers (performing multiline) -> redis -> 5 logstash indexers (performing filters) -> elasticsearch & redis

Often elasticsearch is indexing around 4-9k/sec total

A thread dump from one of the blocked processes can be found here (wasn't sure how to attach a txt file) . www.outtalimits.com.au/jstack.out
After alot of reading, this issue looks potentially related.
#2130

Let me know if you require any further debugging info.

@ph
Copy link
Contributor

ph commented Mar 18, 2015

@seventy-7 Are you running the latest version of the logstash-forwarder too?

@seventy-7
Copy link
Author

@ph yes latest stable. 0.4.0

@ph
Copy link
Contributor

ph commented Mar 18, 2015

Yes this seems related to #2130, usually when this kind of symptom happen is because something block one the output and the back pressure is applied up to the input causing them to block when the queue is full. The internal queue size is 20 items.

  1. Do you have this symptom on 1.4.2?
  2. The logstash reveicers and the logstash indexers aren't the same process?
  3. Can you increase the log verbosity of the logstash receivers with --debug and add any errors you could find?
  4. Any errors on the redis side and which version of redis are you running?

@seventy-7
Copy link
Author

  1. This issue is not present on 1.4.2
  2. These are not the same
  3. Given the issue is not present in 1.4.2, would you like me to proceed with this step for debugging against 1.5.0?
  4. no errors on redis side. 2.8.14

@MarkGavalda
Copy link

I'm seeing the exact same problem. The interesting part is that it only started 3 days ago and prior to that I'd been running the same setup for over a week without any issues! Now I can't keep the logstash indexers running :( The setup is similar to @seventy-7 's: 1.5.0RC2, latest logstash forwarder, redis for queueing between the receiver and indexer logstashes.
The receivers are running as they should, I only have the problem with the indexers.

@ph
Copy link
Contributor

ph commented Apr 14, 2015

@MarkGavalda Would you mind pasting your configuration?

@ph ph self-assigned this Apr 14, 2015
@ph
Copy link
Contributor

ph commented Apr 14, 2015

Similar to #2894

@MarkGavalda
Copy link

Sorry for not updating this earlier, we made many many changes to our whole ES stack since then and the problem went away, however I cannot pinpoint which change was the solution for this issue.

@ph
Copy link
Contributor

ph commented Apr 14, 2015

@MarkGavalda thank your for the update, but just a curiosity are you still running rc2?

@ph
Copy link
Contributor

ph commented Apr 14, 2015

@seventy-7 Could you also share your configuration?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants