Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upLogstash 1.5RC2 stops passing through events, stacktrace included #3136
Comments
suyograo
added
bug
unconfirmed
labels
Apr 30, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
untergeek
Mar 11, 2016
Member
No updates since 1.5RC2, and Logstash is on 2.2.0 now. Closing, but if you feel this is in error, please feel free to open a new issue and reference this one.
Thanks!
|
No updates since 1.5RC2, and Logstash is on 2.2.0 now. Closing, but if you feel this is in error, please feel free to open a new issue and reference this one. Thanks! |
untergeek
closed this
Mar 11, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ianmacl commentedApr 30, 2015
I have a ZeroMQ input and statsd and Elasticsearch output.
Logs: http://pastebin.com/svnJGf7D
Config: http://pastebin.com/E6umv9gq
When I upgraded to 1.5RC2 I found that after some period of time data would no longer make it to ElasticSearch or Statsd. Looking at the network traffic and memory usage it appears that Logstash was continuing to accept traffic but was no longer sending traffic out. I have attached graphs which show this.
This doesn't happen immediately - it generally happens after a number of hours. It also doesn't happen consistently - we have 18 indexers and generally only one or two will go down before we catch it and kick it. I have not yet had a chance to create a test environment in which to replicate this.